We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As reported here, JMESPath.Net does not handle Unicode surrogate pairs.
Consider this character: 😀 (0x1F600).
The following string "😀" is represented in JSON as a pair of encoded surrogate characters like "\uD83D\uDE00".
"😀"
"\uD83D\uDE00"
Internally, JMESPath.Net uses C# which encodes strings using UTF16-LE. However, .NET strings do not handle surrogate pairs correctly.
Please, consider using the StringInfo class for proper support of Unicode in JMESPath.Net.
StringInfo
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
As reported here, JMESPath.Net does not handle Unicode surrogate pairs.
Consider this character: 😀 (0x1F600).
The following string
"😀"
is represented in JSON as a pair of encoded surrogate characters like"\uD83D\uDE00"
.Internally, JMESPath.Net uses C# which encodes strings using UTF16-LE.
However, .NET strings do not handle surrogate pairs correctly.
Please, consider using the
StringInfo
class for proper support of Unicode in JMESPath.Net.The text was updated successfully, but these errors were encountered: