Fix shorthand encoding of Payloads #154
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
dnr
changed the title
cretz
approved these changes
Mar 22, 2024
There was a problem hiding this comment.
Looks great! Let's let @tdeebswihart review too before merging.
| }, { | ||
| name: "empty payloads", | ||
| longformJSON: `{}`, | ||
| shorthandJSON: `null`, |
There was a problem hiding this comment.
An empty array seems "correct" as it is an empty array, but we should support parsing either
dnr
changed the title
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.
What changed?
Marshal/unmarshal empty
Payloadsas[]in shorthand encoding (also acceptnullon unmarshal).Handle the case where one or more
PayloadwithinPayloadscan't be encoded as shorthand.Why?
These cases were producing invalid json.
How did you test it?
unit tests