Ir al contenido principal

JavaScript ES6 Features - Computed Property Names

Sometimes you may want to initialize an object by setting the property names dynamically using strings defined somewhere else. You can use the ES6’s Computed property names for this, in this quick tips episode, you will learn how. Above is the vid and below you will find some useful notes.
  1. 1.


    • Have a browser like Chrome, Edge or Firefox installed
  2. 2.

    Using Computed Property Names in Javascript

    • Initialize and Object with a computed property name
      const fieldName = 'creature';
      let myObject = {
        [fieldName]: '馃悏'
    • Getting the values from the object using the dot or the bracket notation
    • A more complex example of computed property names
      let stuff = {
        ['food' + 1]: '馃崒',
        ['something'.toUpperCase() + 1 + '_function' + 2]: () => '馃徍'
    • Defining Class methods and getters or setters using computed property names
      const aDynamicMethodName = 'weirdHuh',
            aDynamicPropertyName = 'something';
      class SomethinInteresting {
        [aDynamicMethodName]() {
          console.log('Interesting way of naming methods');
        get [aDynamicPropertyName]() {
          return 'a dynamic getter name is born!';
    • Calling the methods or getters using the dot or the bracket notation
      const myNewObject = new SomethinInteresting();
  3. 3.


Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name

Creating a Mongo replicaset using docker: Mongo replicaset + Nodejs + Docker Compose

This is a Docker tutorial for creating a Mongo replica set using docker compose and also a couple more containers to experiment with the replica set, above is the vid and below you will find some of the steps followed. Steps Pre-reqs Have node.js installed And docker installed (make sure you have docker-compose as well) Create a container for defining configurations for a mongo instance Create a container for setting up the replica set Create a simple node app using expressjs and mongoose (A modified version from the previous video ) Create a docker-compose file with the mongo and setup containers and two additional containers for experimenting with the replica set Build, Run and experiment with your new containers Create a dockerfile for the first mongo container (not really needed but you could configure more stuff if needed) Include container with mongo preinstalled:  FROM mongo Create default/working directory:  WORKDIR /usr/src/configs Copy mongo