feat(ServerRendering) support per-request renderers #559
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.
Currently, a renderer is "checked out" for each call to
react_component
. However, if you want some state in that context, it's inefficient: you have to load the state before each call, then clear it after each call.This PR adds support for one-renderer-per-request, so you can load the JS state before rendering the view, then unload it afterwards.
You could do like this:
Of course, you could further generalize this solution with
before_
/after_
/around_action
sTodo
__prerenderer.context