You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rendering nested components on the server-side, an unnecessary network trip is required to make extra requests to the registry itself.
The ideal solution for optimally approaching to this scenario would be to have a plugin to render nested components using exposed registry internals to do the rendering via the same instance.
The api for a server.js file should be something like this:
Whats the plan/priority for this feature? Teams at Chegg are really looking forward to it since half of us are on PHP making it interesting to do rendering part server side.
When rendering nested components on the server-side, an unnecessary network trip is required to make extra requests to the registry itself.
The ideal solution for optimally approaching to this scenario would be to have a plugin to render nested components using exposed registry internals to do the rendering via the same instance.
The api for a
server.js
file should be something like this:The plugin should have the same API as the node.js client's
renderComponents
method - but it should do the rendering without making an extra request to itself.The text was updated successfully, but these errors were encountered: