Enumerable properties mixed with regular properties

[drschwabe]

When you inspect an object the debugger shows enumerable properties in alphabetical order along with regular properties making no visual or practical distinction.

So this is a feature request to be like in Chromium browser's debugger which shows regular properties first, and then lists enumerable properties separtely - and also applies a nice 'grayed out effect' indicating they are enumerable.

[isidorn]

this would require a change in the debug adapter protocol to somehow differentiate enumarable propterties. Due to that assignign to @weinand

[weinand]

@drschwabe with "enumerable properties" you mean numbered properties?

@isidorn in DAP we differentiate already indexed and named properties.

[drschwabe]

Sorry I should clarify, I meant non enumerable properties. They can be thought as a sort of private property. Here's a good overview:

http://zduck.com/2013/non-enumerable-properties-in-javascript/

So for example,

var someObject = {}
Object.defineProperty(someObject, 'someFact', {
      enumerable : false,
      value : 'the sky is blue'
    })

someObject.someFact should be given special treatment in debugger; ie- in Chromium they gray out these properties and show them separately at the bottom of the object's property list when inspecting the object from console or in the variable browser.

In VSCode's debugger right now you have non enumerable properties mixed together.

With Object.define you can also make read only properties ie { writeable : false }
I just did a quick test and VS Code also does not make any distinction with properties defined this way either.

[weinand]

@connor4312 js-debug could surface this information via VariablePresentationHint as internal, readonly.
What do you think?