Editorial: Declare "JSON Serialization Record" #2741
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
bakkot
reviewed
Apr 17, 2022
bakkot
approved these changes
Apr 17, 2022
syg
approved these changes
Apr 27, 2022
michaelficarra
approved these changes
Apr 27, 2022
michaelficarra
added
the
ready to merge
|
(force-pushed to squash in the fixup commit) |
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.
Currently,
JSON.stringifycreates a Record without a named schema, and that gets passed to the_state_parameter (of type 'unknown') of the variousSerializeJSONFoooperations. Instead, declare theJSON Serialization Recordschema for this purpose.