Add handling of _ssr_ prefix state fields #71
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
seriouslysean
approved these changes
Sep 11, 2020
|
@seriouslysean You are absolutely right - this repo is majorly lacking detailed documentation. It's still mostly the docs I wrote up from the original POC I did of this repo. I'm going to file a separate ticket to work on general overall documentation here |
|
@brophdawg11 all good, happy to help if needed 👍 |
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.
Adds support for stripping any Vuex SSR state fields that begin with
_ssr_so that we can use them for memoization of computationally expensive getters methods during SSR since reactvity is disabled during SSR:https://ssr.vuejs.org/guide/universal.html#data-reactivity-on-the-server
vuejs/vue#10151