enhance: State updates from mutate/read now the same #326
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
BREAKING CHANGE: Mutation fetches now result in: - meta entries - results entries
|
Size Change: -121 B (0%) Total Size: 26.7 kB
ℹ️ View Unchanged
|
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.
BREAKING CHANGE: Mutation fetches now result in:
Motivation
Previously fetch keys were simply urls (pre 1.0), so a distinction was needed between mutate and read types. However, for some time now these have serialized to their own unique value. This is the first stage for heavily simplifying the codepaths.
Solution
This means mutates now result in new entries in the state: meta, results. This is likely valuable in some cases.
Open questions
Future path to unify deletes as well?