I have the following idea. When we open a cycle.js visual dev tool, it should be possible to collapse and expand observables' circuits of components. But for this to happen, a visual tool need to know at which point components touch.
This info can be placed by machinery that inserts/remove trees, either taking a name of a component function, that created the tree, and/or by reading annotations on tree-creating function. More so, there can info say at which route (or part of it) has a particular circuit section has been inserted.
Is such labeling done currently? If so, can you point me to code. If not, what do you think about this?
I have the following idea. When we open a cycle.js visual dev tool, it should be possible to collapse and expand observables' circuits of components. But for this to happen, a visual tool need to know at which point components touch.
This info can be placed by machinery that inserts/remove trees, either taking a name of a component function, that created the tree, and/or by reading annotations on tree-creating function. More so, there can info say at which route (or part of it) has a particular circuit section has been inserted.
Is such labeling done currently? If so, can you point me to code. If not, what do you think about this?