Inject by Id (@Id): reimplement the feature
Closed this issue · 1 comments
Currently the feature is implemented asynchronously. It uses two unrelated features-maps and JS call.
We have issues with using two maps : the node becomes attached, detached and attached which is not expected.
We have very serious issues with implementing the feature via JS (call order on the server side and async nature of the code).
So we should not use JS at all for any tree node related features.
The proposition is too use only one dedicated NodeFeature for this feature which makes the node immediately available and handled on the same way as any other node on the client side.
Except that on the client side such nodes requires a special handling.
For all such virtual children features we should use one NodeFeature but introduce a subnamespaces into it.
See details in #2826.
Related : #3058.