| > I may be misunderstanding you I think so, but I probably haven't explained it well. Let's assume the following structure: <Outer>
<EditListElements>
<UIElem>1</UIElem>
<UIElem>2</UIElem>
</EditListElements>
</Outer> Let's say EditListElements is a generic 3rd party component. How does the definition of the props/dependencies of the elements look like? I would like it so that when I define `Outer`, I define some props that outer needs (e.g. let's say it needs an A and a B) and then the actual props to initialize it become A, B and <Props of EditListElements>. But EditListElements is a 3rd party component, which itself derives its properties based on the children it uses. And so on. One of the reasons to do it like this is that if I have a big, nested graph of components and I add a required dependency value to some component down the graph then all the intermediate components should have the props "automatically" updated and I will have to pass it to one of those components (potentially the very toplevel component) to satisfy the compiler. Then, it will be passed down automatically to where it is needed. The way this is currently "solved" in react most of the time is to move those required values to some global store or so which is then accessed or at least accessible by all components. It quickly leads to a big ball of mud and it is tricky to see what a component needs (and what it doesn't need) by just looking at the component in the graph. Hope that makes it more clear. |