Support for multibyte characters in ParserError exception messages
#755
Labels
Comments
|
That's a good point. |
byroot
added a commit
to byroot/json
that referenced
this issue
Feb 25, 2025
Fix: ruby#755 Error messages now include a snippet of the document that doesn't parse to help locate the issue, however the way it was done wasn't UTF-8 aware, and it could result in exception messages with truncated characters. It would be nice to go a bit farther and actually support codepoints, but it's a lot of complexity to do it in C, perhaps if we move that logic to Ruby given it's not a performance sensitive codepath.
|
Thanks for the quick response! |
matzbot
pushed a commit
to ruby/ruby
that referenced
this issue
Feb 27, 2025
Fix: ruby/json#755 Error messages now include a snippet of the document that doesn't parse to help locate the issue, however the way it was done wasn't UTF-8 aware, and it could result in exception messages with truncated characters. It would be nice to go a bit farther and actually support codepoints, but it's a lot of complexity to do it in C, perhaps if we move that logic to Ruby given it's not a performance sensitive codepath. ruby/json@e144793b72
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since v2.7.3, the size of
ParserErrorexception messages is limited to 32 bytes.When using multibyte characters, the characters might be cut off in the middle of a byte.
This could potentially cause additional unexpected errors.
Would it be possible to change the limit from byte size to character count?
The text was updated successfully, but these errors were encountered: