How to get object tree presentation of components tree before initial render?

[roman01la]

One way I've found is to apply a mixin to every component which takes _rootNodeID, treat it as path and construct an object. But _rootNodeID includes ids not only of React components, but elements as well.

[syranide]

Why do you need this?

[roman01la]

I'm experimenting with a concept of global state object, where it should be programmatically constructed to represent hierarchy of components tree. Thus it's easier to pass state as props from root component down the tree.

[sophiebits]

Not sure what you mean. Can you give a code example of the problem you're trying to solve?

[iamdustan]

Related, is there a way to traverse the render tree before rendering?
E.g. how does GraphQL work? https://twitter.com/iamdustan/status/571328094398779395

Does it do ahead of time tree traversal pulling the statics: {queries: {}} calls out or use a mixin for every component with graphql calls?

[roman01la]

@iamdustan yeah, this is somewhat my question.
@spicyj Ok, check this thread, the idea is to use a hierarchical object that mirrors components tree of the app.

[gaearon]

Closing as the tree is considered an implementation detail.

[reverofevil]

@gaearon Is it possible to have React without a component tree? Could you reconsider, please?

Public API for a component tree traversal would allow writing (de)serializers to rehydrate without resorting to a global state.

[gaearon]

We’re aware of use cases—please see #4595 for a place to discuss this.

Right now we’re in the middle of a React rewrite (https://www.youtube.com/watch?v=aV1271hd9ew) so it's not a very good time for us to expose any internals.