Support configurable JsonSerializerOptions #67
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
TechnoBerry
reviewed
Nov 13, 2023
|
Hello @anserg256! Thank you for your PR! I just looked at the proposed changes and described a small suggestion |
|
Thank you for your contribution! |
|
I just published a release with your PR |
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.
Hello!
The JSON serialization doesn't seem to support cyrillic or any additional unicode ranges.
For example, the word "Тест" would appear as "\u0422\u0435\u0441\u0442".
I'd like to propose a way to customize the encoder or other JsonSerializerOptions used in the client.