CS: Implement SSR compatible dapper context #744
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Implement a workaround for the lack of React Context support on the NextJS serverside rendering process. Context isn't supported as it's often used for state management, but in our case we just need a way to provide the dapper implementation into some global scope which can later be consumed by the components without direct references to the implementation. The implemented workaround relies on globalThis if it's available (server, newer browsers) or window if it isn't (older browsers). globalThis might persist throughout multiple requests served by the NextJS server, meaning instance-wide serverside caching should be possible to implement in dapper.
MythicManiac
force-pushed
the
ssr-context
branch
from
758927b to
cec3683
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implement a workaround for the lack of React Context support on the NextJS serverside rendering process. Context isn't supported as it's often used for state management, but in our case we just need a way to provide the dapper implementation into some global scope which can later be consumed by the components without direct references to the implementation.
The implemented workaround relies on globalThis if it's available (server, newer browsers) or window if it isn't (older browsers). globalThis might persist throughout multiple requests served by the NextJS server, meaning instance-wide serverside caching should be possible to implement in dapper.