Added registry server loader feature #7443
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ok, I could not help it. I had this idea (a subsequent PR which uses this is coming):
What if I want configuration that only is loaded in the server, because it's releated to loaders? What if we offload the config to not be in the bundle, but backend powered, loaded in loaders. So we free the client config from it. Still to be seen, but what if we can offload there all the component registry, serve it only when it's needed via RSCs?
And, regarding the next PR. What if my add-on wants to add things to the root loader? as in, gimme some extra info from the backend? eg. a slot that gets some extra data.
I think also that if we succeed with this, we can use it for separate PublicUI config from CMSUI config (eg. blocks).
📚 Documentation preview 📚: https://volto--7443.org.readthedocs.build/