-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[Feature request] An ability to filter out decorations in the tree #379
Comments
Is the tree frustrating to you or only the list at the bottom? |
I would be a big fan of the second image, @spicyj. Happy to PR it next week. |
@spicyj both are frustrating for my taste. Bottom list is weird but it's usable at least. I've seen more deep trees in practice, and at some point it's not usable (I'm about the tree itself). Worse that as you can see, stacked containers add more than 50% of deepness (look at the first lines in the list at the bottom). I think, it would be nice if we'll find a way how to flatten them out of the tree. For example, we could have a button to stack components w/o DOM elements in between. |
What I like about the current tree is that it gives a very clear image of what components are nested and direct access to all of them. I'm curious to see mocks/sketches of how this could be more compact without suffering by hiding too much information. |
Some discussion happening in #503. |
Closing in favor of #604 (it's a bit more fresh). |
First I'll just define a problem which me (and, not only me) faced..
It turns out that it's common today to have a deeply nested components thee. In many ways, it becomes as it is due to a heavy usage of decorators of any kind or/and other 'compositions'.
As an example (not a weirdest case):
I think, it would be nice to have an ability to filter out decorators-like
components from the three based on some criteria (could be user-defined, I guess).
The text was updated successfully, but these errors were encountered: