It should be possible to return useValue from a Component directly. It probably is not possible right now, because that in theory would require to update Component's tree to have that new HTML node.
Potential solution
Right now nodes know about their parent elements, but not components (the full tree is available only going up). It should not be too hard to include that information, because we don't need to iterate, only the direct parent is relevant (if components are nested, top level components' tree won't change, it will be a child component).
I think it is better to address this issue (or decide not to support it officially) after dealing with #34, which is definitely a required feature, the way the Context will be implemented might affect what is available to child components.
Description
It should be possible to return
useValuefrom a Component directly. It probably is not possible right now, because that in theory would require to update Component'streeto have that new HTML node.Potential solution
Right now nodes know about their parent elements, but not components (the full tree is available only going up). It should not be too hard to include that information, because we don't need to iterate, only the direct parent is relevant (if components are nested, top level components'
treewon't change, it will be a child component).I think it is better to address this issue (or decide not to support it officially) after dealing with #34, which is definitely a required feature, the way the Context will be implemented might affect what is available to child components.