- Fix bug where the number of nodes added when clicking the ellipsis
node would double each time.
- Fix duplicate ellipsis nodes when collapsing and expanding.
- Fix other nodes being added when collapsing and expanding.
New nodes should only be added when initially expanding, or when
clicking the ellipsis node.
- `count` now includes filtered out keys.
- Fix accidentally escaped `[link]` markup
(broken in 1dbf02e941)
- Using Text type will help avoid this problem in the future.
Don't just make it work, make it so it must work!
Make it strongly typed, not stringly typed.
- Use `css_identifier_styled` instead of `css_identifier`
- Add colors to exceptional case handling
I just came across this `css_path_nodes` property and realized my path
was probably in the wrong order.
Also, this gives a clear option for naming the variable,
although I feel I should point out it's not a different type of node.
- Include bytes as one of the basic types.
- Use ReprHighlighter everywhere repr is used.
- Show length for sets and tuples as well as lists.
- Show repr for lists.
- Bold key and show "=" for lists/dicts and other objects.
- Allow expanding tuples and sets.
- Remove "{}" and "[]" markers for easier scanning.
- DRY adding nodes with enumerate() vs dir()
- Don't show the error message as a quoted string value
(This was super simple, but ambiguous and potentially confusing.)
- Make the error handling look nice with colors
- Make the Tree into a subclass, PropertiesTree.
- Populate nodes when expanding a node instead of all at once.
- Remove the max_depth limit, since you now expand nodes manually.
- Remove cyclic reference detection, for now at least.
- Track already-loaded nodes/keys, like in the DOMTree, but with a data
structure. It's a little more complicated since unlike DOM nodes, a
value could appear multiple times in a list. But this should also
be more efficient.
- I wanted it to expand all, not just one level
(but named it according to how it ended up functioning.)
- It's not that helpful since the Inspect Element feature works great.
- It's especially confusing now that there's multiple tree views.
It doesn't affect the Properties view, but it's not visually tied to
the DOM tree view except by proximity.
- I'd rather make the DOM tree default to (mostly) expanded, rather than
have a button you have to click, anyways.
