fix: correct json codec links & bytes handling #472
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
willscott
approved these changes
Oct 13, 2022
The plain JSON codec shouldn't be able to encode bytes or links and should consistently error. The DAG-JSON codec should be able to, of course.
rvagg
force-pushed
the
rvagg/json-links-and-bytes
branch
from
68536ca
to
a9f2fcb
Compare
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.
The plain JSON codec shouldn't be able to encode bytes or links and should consistently error. The DAG-JSON codec should be able to, of course.
I'll do a simple 0.18.1 after this, but in a separate PR that updates the changelog and does the proper release process.