refactor: Optomise how page data is updated #1380
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
Each inventory page is now a seperate array in the store that can be updated on its own. As opposed to a large ggCharacters object having to be updated regardless of which page changed. Then instead of always creating a costly mutative 'create' object the checks for new data are done first. If the data changes then then mutative is used.
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.
Each inventory page is now a seperate array in the store that can be updated on its own. As opposed to a large ggCharacters object having to be updated regardless of which page changed.
Then instead of always creating a costly mutative 'create' object the checks for new data are done first. If the data changes then then mutative is used.