Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: marshal \b and \f properly #25

Merged
merged 2 commits into from
Aug 21, 2024
Merged

fix: marshal \b and \f properly #25

merged 2 commits into from
Aug 21, 2024

Conversation

kruskall
Copy link
Member

writer wasn't encoding \b and \f causing some diff with the upstream json package.
Update switch and add test to validate all utf8 runes are encoded correctly

Closes #22

writer wasn't encoding \b and \f causing some diff with
the upstream json package.
Update switch and add test to validate all utf8 runes are
encoded correctly
@kruskall kruskall requested a review from a team August 12, 2024 12:47
1pkg
1pkg previously approved these changes Aug 12, 2024
@kruskall kruskall requested a review from a team August 19, 2024 09:10
@kruskall
Copy link
Member Author

This issue was fixed upstream in go 1.22 so we need to require go >= 1.22 to make sure we match the go stdlib json package

@kruskall kruskall merged commit bc4661e into main Aug 21, 2024
3 checks passed
@kruskall kruskall deleted the fix/missing-bytes branch August 21, 2024 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Diff with upstream string marshaling code
2 participants