You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
util: unenumerable properties should be visible #1598
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?
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.
I think we could change showHidden to default to true, with special handling to hide language builtin unenumerable properties. This would be pretty much what the Chrome console now does. If we agree on that, I can do a PR.
I think we could change showHidden to default to true
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 showHidden flipped just on the REPL to make this work seems wrong. Also, blue ansi color is unreadable on Windows according to a comment. If we ever decide to add 256 color support to inspect, we might be able to revisit this issue.
Activity
petkaantonov commentedon May 3, 2015
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?
silverwind commentedon May 3, 2015
True, one could do something like
[Getter/enumerable], but I think that could be too verbose.As I see it, everything is better than
{}.monsanto commentedon May 3, 2015
This is intentional, unenumerable properties need the
showHiddenflag set to show: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.
silverwind commentedon May 3, 2015
Interesting. This is what Firefox does:
bnoordhuis commentedon Jun 6, 2015
Ping @silverwind, what is the status of this issue?
silverwind commentedon Jun 6, 2015
I think we could change
showHiddento default to true, with special handling to hide language builtin unenumerable properties. This would be pretty much what the Chrome console now does. If we agree on that, I can do a PR.vkurchatkin commentedon Jun 6, 2015
-1 from me. I don't think we should try to replicate Chrome console
chrisdickinson commentedon Jun 6, 2015
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.
silverwind commentedon Jun 7, 2015
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).
silverwind commentedon Aug 22, 2015
Decided against pursuing this further because having
showHiddenflipped just on the REPL to make this work seems wrong. Also, blue ansi color is unreadable on Windows according to a comment. If we ever decide to add 256 color support to inspect, we might be able to revisit this issue.