-
Notifications
You must be signed in to change notification settings - Fork 30.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
util: unenumerable properties should be visible #1598
Comments
Though these views are not equivalent. The equivalent view in chrome is when you expand the properties and in that view the unenumerable properties are greyed out. Perhaps there should be some kind of enumerability marker in the util view as well? |
True, one could do something like As I see it, everything is better than |
This is intentional, unenumerable properties need the
although I guess whether or not this is desirable is up for discussion. Keep in mind on the REPL this would get obnoxious quick since arrays would show their length attribute. |
Interesting. This is what Firefox does: > var o = {}; Object.defineProperty(o, "a", {get: function(){}})
Object { , 1 more… }
> var o = {}; Object.defineProperty(o, "a", {get: function(){}, enumerable:true})
Object { a: Getter } |
Ping @silverwind, what is the status of this issue? |
I think we could change |
-1 from me. I don't think we should try to replicate Chrome console |
I'm not opposed to either making it default to true for the REPL/console only. Where ansi colors are enabled we should probably use them to indicate non-enumerability of properties as well. |
Yeah, would keep it REPL-only. I could see property names colored blue as normal properties and magenta as unenumerable ones. Right now, we only color the value (yellow). |
Decided against pursuing this further because having |
Same in Chrome:
cc: @monsanto
The text was updated successfully, but these errors were encountered: