Make sure generated keys include defaults #366
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
timostamm
approved these changes
May 6, 2024
Merged
paul-sachs
added a commit
that referenced
this pull request
May 10, 2024
## What's Changed * Need mutation context generic to support passing context by @paul-sachs in #359 * Make sure generated keys include defaults by @paul-sachs in #366 **Full Changelog**: v1.3.1...v1.4.0
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.
With the current state, a generated key for a message with undefined fields and one with defined (but matching the default) fields will be different, meaning that duplicate requests can be made. This change ensures that all keys generated take into account default fields.
Fixes #361