Strange behavior of Object.defineProperty() in JavaScriptCreate GUID / UUID in JavaScript?How do JavaScript closures work?What is the most efficient way to deep clone an object in JavaScript?How do I remove a property from a JavaScript object?Which equals operator (== vs ===) should be used in JavaScript comparisons?How do I include a JavaScript file in another JavaScript file?What does “use strict” do in JavaScript, and what is the reasoning behind it?How to check whether a string contains a substring in JavaScript?How do I remove a particular element from an array in JavaScript?For-each over an array in JavaScript?

How to stop co-workers from teasing me because I know Russian?

Could the terminal length of components like resistors be reduced?

a sore throat vs a strep throat vs strep throat

Function pointer with named arguments?

How to fry ground beef so it is well-browned

Check if a string is entirely made of the same substring

What are the steps to solving this definite integral?

Is there any official lore on the Far Realm?

Pre-plastic human skin alternative

Retract an already submitted recommendation letter (written for an undergrad student)

Initiative: Do I lose my attack/action if my target moves or dies before my turn in combat?

Why do games have consumables?

Read line from file and process something

What is the smallest unit of eos?

Don’t seats that recline flat defeat the purpose of having seatbelts?

Did the BCPL programming language support floats?

How much cash can I safely carry into the USA and avoid civil forfeiture?

What term is being referred to with "reflected-sound-of-underground-spirits"?

How to have a sharp product image?

Like totally amazing interchangeable sister outfits II: The Revenge

What happened to Captain America in Endgame?

Was there a Viking Exchange as well as a Columbian one?

Overlay of two functions leaves gaps

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?



Strange behavior of Object.defineProperty() in JavaScript


Create GUID / UUID in JavaScript?How do JavaScript closures work?What is the most efficient way to deep clone an object in JavaScript?How do I remove a property from a JavaScript object?Which equals operator (== vs ===) should be used in JavaScript comparisons?How do I include a JavaScript file in another JavaScript file?What does “use strict” do in JavaScript, and what is the reasoning behind it?How to check whether a string contains a substring in JavaScript?How do I remove a particular element from an array in JavaScript?For-each over an array in JavaScript?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








54















I was playing with below javascript code. Understanding of Object.defineProperty() and I am facing a strange issue with it. When I try to execute below code in the browser or in the VS code the output is not as expected whereas if I try to debug the code the output is correct



When I debug the code and evaluate the profile I can see the name & age property in the object
But at the time of output, it only shows the name property






//Code Snippet 
let profile =
name: 'Barry Allen',


// I added a new property in the profile object.
Object.defineProperty(profile, 'age',
value: 23,
writable: true
)

console.log(profile)
console.log(profile.age)





Now expected output here should be



name: "Barry Allen", age: 23
23


but I get the output as.
Note that I am able to access the age property defined afterwards.
I am not sure why the console.log() is behaving this way.



name: "Barry Allen"
23









share|improve this question






























    54















    I was playing with below javascript code. Understanding of Object.defineProperty() and I am facing a strange issue with it. When I try to execute below code in the browser or in the VS code the output is not as expected whereas if I try to debug the code the output is correct



    When I debug the code and evaluate the profile I can see the name & age property in the object
    But at the time of output, it only shows the name property






    //Code Snippet 
    let profile =
    name: 'Barry Allen',


    // I added a new property in the profile object.
    Object.defineProperty(profile, 'age',
    value: 23,
    writable: true
    )

    console.log(profile)
    console.log(profile.age)





    Now expected output here should be



    name: "Barry Allen", age: 23
    23


    but I get the output as.
    Note that I am able to access the age property defined afterwards.
    I am not sure why the console.log() is behaving this way.



    name: "Barry Allen"
    23









    share|improve this question


























      54












      54








      54


      5






      I was playing with below javascript code. Understanding of Object.defineProperty() and I am facing a strange issue with it. When I try to execute below code in the browser or in the VS code the output is not as expected whereas if I try to debug the code the output is correct



      When I debug the code and evaluate the profile I can see the name & age property in the object
      But at the time of output, it only shows the name property






      //Code Snippet 
      let profile =
      name: 'Barry Allen',


      // I added a new property in the profile object.
      Object.defineProperty(profile, 'age',
      value: 23,
      writable: true
      )

      console.log(profile)
      console.log(profile.age)





      Now expected output here should be



      name: "Barry Allen", age: 23
      23


      but I get the output as.
      Note that I am able to access the age property defined afterwards.
      I am not sure why the console.log() is behaving this way.



      name: "Barry Allen"
      23









      share|improve this question
















      I was playing with below javascript code. Understanding of Object.defineProperty() and I am facing a strange issue with it. When I try to execute below code in the browser or in the VS code the output is not as expected whereas if I try to debug the code the output is correct



      When I debug the code and evaluate the profile I can see the name & age property in the object
      But at the time of output, it only shows the name property






      //Code Snippet 
      let profile =
      name: 'Barry Allen',


      // I added a new property in the profile object.
      Object.defineProperty(profile, 'age',
      value: 23,
      writable: true
      )

      console.log(profile)
      console.log(profile.age)





      Now expected output here should be



      name: "Barry Allen", age: 23
      23


      but I get the output as.
      Note that I am able to access the age property defined afterwards.
      I am not sure why the console.log() is behaving this way.



      name: "Barry Allen"
      23





      //Code Snippet 
      let profile =
      name: 'Barry Allen',


      // I added a new property in the profile object.
      Object.defineProperty(profile, 'age',
      value: 23,
      writable: true
      )

      console.log(profile)
      console.log(profile.age)





      //Code Snippet 
      let profile =
      name: 'Barry Allen',


      // I added a new property in the profile object.
      Object.defineProperty(profile, 'age',
      value: 23,
      writable: true
      )

      console.log(profile)
      console.log(profile.age)






      javascript






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 19 at 10:32









      Pierre44

      1,3101423




      1,3101423










      asked Apr 19 at 5:36









      Ravi WRavi W

      27327




      27327






















          3 Answers
          3






          active

          oldest

          votes


















          64














          You should set enumerable to true. In Object.defineProperty its false by default. According to MDN.




          enumerable

          true if and only if this property shows up during enumeration of the properties on the corresponding object.

          Defaults to false.




          Non-enumerable means that property will not be shown in Object.keys() or for..in loop neither in console






          let profile = 
          name: 'Barry Allen',


          // I added a new property in the profile object.

          Object.defineProperty(profile , 'age',
          value: 23,
          writable: true,
          enumerable: true
          )
          console.log(profile)
          console.log(profile.age)





          All the properties and methods on prototype object of built-in classes are non-enumerable. Thats is the reason you can call them from instance but they don't appear while iterating.



          To get all properties(including non-enumerable)Object​.get​OwnProperty​Names()
          .






          let profile = 
          name: 'Barry Allen',


          // I added a new property in the profile object.

          Object.defineProperty(profile , 'age',
          value: 23,
          writable: true,
          enumerable: false
          )
          for(let key in profile) console.log(key) //only name will be displayed.

          console.log(Object.getOwnPropertyNames(profile)) //You will se age too








          share|improve this answer

























          • I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

            – randomSoul
            Apr 19 at 5:48











          • @randomSoul I can't get what you mean.

            – Maheer Ali
            Apr 19 at 5:54







          • 1





            See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

            – randomSoul
            Apr 19 at 5:59







          • 7





            @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

            – Yong Quan
            Apr 19 at 6:20







          • 3





            @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

            – Mike Caron
            Apr 19 at 16:16


















          18














          By default, properties you define with defineProperty are not enumerable - this means that they will not show up when you iterate over their Object.keys (which is what the snippet console does). (Similarly, the length property of an array does not get displayed, because it's non-enumerable.)



          See MDN:




          enumerable



          true if and only if this property shows up during enumeration of the properties on the corresponding object.



          Defaults to false.




          Make it enumerable instead:






          //Code Snippet 
          let profile =
          name: 'Barry Allen',


          // I added a new property in the profile object.
          Object.defineProperty(profile, 'age',
          value: 23,
          writable: true,
          enumerable: true
          )

          console.log(profile)
          console.log(profile.age)





          The reason you can see the property in the logged image is that Chrome's console will show you non-enumerable properties as well - but the non-enumerable properties will be slightly greyed-out:



          enter image description here



          See how age is grey-ish, while name is not - this indicates that name is enumerable, and age is not.






          share|improve this answer

























          • Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

            – Maheer Ali
            Apr 19 at 6:11







          • 3





            Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

            – CertainPerformance
            Apr 19 at 6:17


















          4














          Whenever you use".defineProperty" method of object. You should better define all the properties of the descriptor. Because if you don't define other property descriptor then it assumes default values for all of them which is false. So your console.log checks for all the enumerable : true properties and logs them.



          //Code Snippet 
          let profile =
          name: 'Barry Allen',


          // I added a new property in the profile object.
          Object.defineProperty(profile, 'age',
          value: 23,
          writable: true,
          enumerable : true,
          configurable : true
          )

          console.log(profile)
          console.log(profile.age)





          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55757089%2fstrange-behavior-of-object-defineproperty-in-javascript%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            64














            You should set enumerable to true. In Object.defineProperty its false by default. According to MDN.




            enumerable

            true if and only if this property shows up during enumeration of the properties on the corresponding object.

            Defaults to false.




            Non-enumerable means that property will not be shown in Object.keys() or for..in loop neither in console






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            All the properties and methods on prototype object of built-in classes are non-enumerable. Thats is the reason you can call them from instance but they don't appear while iterating.



            To get all properties(including non-enumerable)Object​.get​OwnProperty​Names()
            .






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too








            share|improve this answer

























            • I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

              – randomSoul
              Apr 19 at 5:48











            • @randomSoul I can't get what you mean.

              – Maheer Ali
              Apr 19 at 5:54







            • 1





              See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

              – randomSoul
              Apr 19 at 5:59







            • 7





              @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

              – Yong Quan
              Apr 19 at 6:20







            • 3





              @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

              – Mike Caron
              Apr 19 at 16:16















            64














            You should set enumerable to true. In Object.defineProperty its false by default. According to MDN.




            enumerable

            true if and only if this property shows up during enumeration of the properties on the corresponding object.

            Defaults to false.




            Non-enumerable means that property will not be shown in Object.keys() or for..in loop neither in console






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            All the properties and methods on prototype object of built-in classes are non-enumerable. Thats is the reason you can call them from instance but they don't appear while iterating.



            To get all properties(including non-enumerable)Object​.get​OwnProperty​Names()
            .






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too








            share|improve this answer

























            • I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

              – randomSoul
              Apr 19 at 5:48











            • @randomSoul I can't get what you mean.

              – Maheer Ali
              Apr 19 at 5:54







            • 1





              See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

              – randomSoul
              Apr 19 at 5:59







            • 7





              @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

              – Yong Quan
              Apr 19 at 6:20







            • 3





              @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

              – Mike Caron
              Apr 19 at 16:16













            64












            64








            64







            You should set enumerable to true. In Object.defineProperty its false by default. According to MDN.




            enumerable

            true if and only if this property shows up during enumeration of the properties on the corresponding object.

            Defaults to false.




            Non-enumerable means that property will not be shown in Object.keys() or for..in loop neither in console






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            All the properties and methods on prototype object of built-in classes are non-enumerable. Thats is the reason you can call them from instance but they don't appear while iterating.



            To get all properties(including non-enumerable)Object​.get​OwnProperty​Names()
            .






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too








            share|improve this answer















            You should set enumerable to true. In Object.defineProperty its false by default. According to MDN.




            enumerable

            true if and only if this property shows up during enumeration of the properties on the corresponding object.

            Defaults to false.




            Non-enumerable means that property will not be shown in Object.keys() or for..in loop neither in console






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            All the properties and methods on prototype object of built-in classes are non-enumerable. Thats is the reason you can call them from instance but they don't appear while iterating.



            To get all properties(including non-enumerable)Object​.get​OwnProperty​Names()
            .






            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too








            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: true
            )
            console.log(profile)
            console.log(profile.age)





            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too





            let profile = 
            name: 'Barry Allen',


            // I added a new property in the profile object.

            Object.defineProperty(profile , 'age',
            value: 23,
            writable: true,
            enumerable: false
            )
            for(let key in profile) console.log(key) //only name will be displayed.

            console.log(Object.getOwnPropertyNames(profile)) //You will se age too






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 2 days ago

























            answered Apr 19 at 5:38









            Maheer AliMaheer Ali

            13.1k1330




            13.1k1330












            • I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

              – randomSoul
              Apr 19 at 5:48











            • @randomSoul I can't get what you mean.

              – Maheer Ali
              Apr 19 at 5:54







            • 1





              See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

              – randomSoul
              Apr 19 at 5:59







            • 7





              @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

              – Yong Quan
              Apr 19 at 6:20







            • 3





              @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

              – Mike Caron
              Apr 19 at 16:16

















            • I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

              – randomSoul
              Apr 19 at 5:48











            • @randomSoul I can't get what you mean.

              – Maheer Ali
              Apr 19 at 5:54







            • 1





              See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

              – randomSoul
              Apr 19 at 5:59







            • 7





              @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

              – Yong Quan
              Apr 19 at 6:20







            • 3





              @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

              – Mike Caron
              Apr 19 at 16:16
















            I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

            – randomSoul
            Apr 19 at 5:48





            I didn't knew about this, but when I checked by running the local code in browser, it shows up perfectly (in spite of explicitly specifying enumerable to false).

            – randomSoul
            Apr 19 at 5:48













            @randomSoul I can't get what you mean.

            – Maheer Ali
            Apr 19 at 5:54






            @randomSoul I can't get what you mean.

            – Maheer Ali
            Apr 19 at 5:54





            1




            1





            See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

            – randomSoul
            Apr 19 at 5:59






            See - pasteboard.co/IaOxMqB.png . I did not set enumerable to true for age, but still it is shown.

            – randomSoul
            Apr 19 at 5:59





            7




            7





            @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

            – Yong Quan
            Apr 19 at 6:20






            @randomSoul In Chrome console, you should see unenumerable properties colored a little bit transparent.

            – Yong Quan
            Apr 19 at 6:20





            3




            3





            @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

            – Mike Caron
            Apr 19 at 16:16





            @randomSoul That's a debugging feature, not a language feature. If you change the example to use JSON.stringify it will behave consistently, and omit the non-enumerable properties.

            – Mike Caron
            Apr 19 at 16:16













            18














            By default, properties you define with defineProperty are not enumerable - this means that they will not show up when you iterate over their Object.keys (which is what the snippet console does). (Similarly, the length property of an array does not get displayed, because it's non-enumerable.)



            See MDN:




            enumerable



            true if and only if this property shows up during enumeration of the properties on the corresponding object.



            Defaults to false.




            Make it enumerable instead:






            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)





            The reason you can see the property in the logged image is that Chrome's console will show you non-enumerable properties as well - but the non-enumerable properties will be slightly greyed-out:



            enter image description here



            See how age is grey-ish, while name is not - this indicates that name is enumerable, and age is not.






            share|improve this answer

























            • Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

              – Maheer Ali
              Apr 19 at 6:11







            • 3





              Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

              – CertainPerformance
              Apr 19 at 6:17















            18














            By default, properties you define with defineProperty are not enumerable - this means that they will not show up when you iterate over their Object.keys (which is what the snippet console does). (Similarly, the length property of an array does not get displayed, because it's non-enumerable.)



            See MDN:




            enumerable



            true if and only if this property shows up during enumeration of the properties on the corresponding object.



            Defaults to false.




            Make it enumerable instead:






            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)





            The reason you can see the property in the logged image is that Chrome's console will show you non-enumerable properties as well - but the non-enumerable properties will be slightly greyed-out:



            enter image description here



            See how age is grey-ish, while name is not - this indicates that name is enumerable, and age is not.






            share|improve this answer

























            • Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

              – Maheer Ali
              Apr 19 at 6:11







            • 3





              Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

              – CertainPerformance
              Apr 19 at 6:17













            18












            18








            18







            By default, properties you define with defineProperty are not enumerable - this means that they will not show up when you iterate over their Object.keys (which is what the snippet console does). (Similarly, the length property of an array does not get displayed, because it's non-enumerable.)



            See MDN:




            enumerable



            true if and only if this property shows up during enumeration of the properties on the corresponding object.



            Defaults to false.




            Make it enumerable instead:






            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)





            The reason you can see the property in the logged image is that Chrome's console will show you non-enumerable properties as well - but the non-enumerable properties will be slightly greyed-out:



            enter image description here



            See how age is grey-ish, while name is not - this indicates that name is enumerable, and age is not.






            share|improve this answer















            By default, properties you define with defineProperty are not enumerable - this means that they will not show up when you iterate over their Object.keys (which is what the snippet console does). (Similarly, the length property of an array does not get displayed, because it's non-enumerable.)



            See MDN:




            enumerable



            true if and only if this property shows up during enumeration of the properties on the corresponding object.



            Defaults to false.




            Make it enumerable instead:






            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)





            The reason you can see the property in the logged image is that Chrome's console will show you non-enumerable properties as well - but the non-enumerable properties will be slightly greyed-out:



            enter image description here



            See how age is grey-ish, while name is not - this indicates that name is enumerable, and age is not.






            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)





            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable: true
            )

            console.log(profile)
            console.log(profile.age)






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Apr 19 at 6:16

























            answered Apr 19 at 5:39









            CertainPerformanceCertainPerformance

            102k166393




            102k166393












            • Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

              – Maheer Ali
              Apr 19 at 6:11







            • 3





              Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

              – CertainPerformance
              Apr 19 at 6:17

















            • Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

              – Maheer Ali
              Apr 19 at 6:11







            • 3





              Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

              – CertainPerformance
              Apr 19 at 6:17
















            Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

            – Maheer Ali
            Apr 19 at 6:11






            Someone give this pasteboard.co/IaOxMqB.png Its showing age property in chrome console. Can you please explain that? Does chrome console works differently?

            – Maheer Ali
            Apr 19 at 6:11





            3




            3





            Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

            – CertainPerformance
            Apr 19 at 6:17





            Yes, that's a Chrome console behavior - it'll show you all properties, including non-enumerable ones, see edit. The non-enumerable properties (like age and __proto__) will be slightly greyed out.

            – CertainPerformance
            Apr 19 at 6:17











            4














            Whenever you use".defineProperty" method of object. You should better define all the properties of the descriptor. Because if you don't define other property descriptor then it assumes default values for all of them which is false. So your console.log checks for all the enumerable : true properties and logs them.



            //Code Snippet 
            let profile =
            name: 'Barry Allen',


            // I added a new property in the profile object.
            Object.defineProperty(profile, 'age',
            value: 23,
            writable: true,
            enumerable : true,
            configurable : true
            )

            console.log(profile)
            console.log(profile.age)





            share|improve this answer



























              4














              Whenever you use".defineProperty" method of object. You should better define all the properties of the descriptor. Because if you don't define other property descriptor then it assumes default values for all of them which is false. So your console.log checks for all the enumerable : true properties and logs them.



              //Code Snippet 
              let profile =
              name: 'Barry Allen',


              // I added a new property in the profile object.
              Object.defineProperty(profile, 'age',
              value: 23,
              writable: true,
              enumerable : true,
              configurable : true
              )

              console.log(profile)
              console.log(profile.age)





              share|improve this answer

























                4












                4








                4







                Whenever you use".defineProperty" method of object. You should better define all the properties of the descriptor. Because if you don't define other property descriptor then it assumes default values for all of them which is false. So your console.log checks for all the enumerable : true properties and logs them.



                //Code Snippet 
                let profile =
                name: 'Barry Allen',


                // I added a new property in the profile object.
                Object.defineProperty(profile, 'age',
                value: 23,
                writable: true,
                enumerable : true,
                configurable : true
                )

                console.log(profile)
                console.log(profile.age)





                share|improve this answer













                Whenever you use".defineProperty" method of object. You should better define all the properties of the descriptor. Because if you don't define other property descriptor then it assumes default values for all of them which is false. So your console.log checks for all the enumerable : true properties and logs them.



                //Code Snippet 
                let profile =
                name: 'Barry Allen',


                // I added a new property in the profile object.
                Object.defineProperty(profile, 'age',
                value: 23,
                writable: true,
                enumerable : true,
                configurable : true
                )

                console.log(profile)
                console.log(profile.age)






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Apr 19 at 5:41









                RK_15RK_15

                63910




                63910



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55757089%2fstrange-behavior-of-object-defineproperty-in-javascript%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to write a 12-bar blues melodyI-IV-V blues progressionHow to play the bridges in a standard blues progressionHow does Gdim7 fit in C# minor?question on a certain chord progressionMusicology of Melody12 bar blues, spread rhythm: alternative to 6th chord to avoid finger stretchChord progressions/ Root key/ MelodiesHow to put chords (POP-EDM) under a given lead vocal melody (starting from a good knowledge in music theory)Are there “rules” for improvising with the minor pentatonic scale over 12-bar shuffle?Confusion about blues scale and chords

                    What if the end-user didn't have the required library?What is setup.py?What is a clean, pythonic way to have multiple constructors in Python?What does Ruby have that Python doesn't, and vice versa?What is the reason for having '//' in Python?How do I create a namespace package in Python?How to package shared objects that python modules depend on?setuptools vs. distutils: why is distutils still a thing?Navigation in Windows 10 vs code not going to virtualenv library when the same library is installed at user levelPython create package for local usePackaging a project that uses multiple python versionsWhy is permission denied on pip install except for when “--user” is included at end of command?

                    Esgonzo ibérico Índice Descrición Distribución Hábitat Ameazas Notas Véxase tamén "Acerca dos nomes dos anfibios e réptiles galegos""Chalcides bedriagai"Chalcides bedriagai en Carrascal, L. M. Salvador, A. (Eds). Enciclopedia virtual de los vertebrados españoles. Museo Nacional de Ciencias Naturales, Madrid. España.Fotos