Make ensure_ascii
Dynamic with Default Set to True
in JSON Serialization
#168
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.
Description of change
This PR introduces a dynamic setting for the ensure_ascii parameter in the
json.dumps
function, with its default value set toTrue
. This change allows for greater flexibility in JSON serialization, enabling non-ASCII characters to be preserved when needed by explicitly passingensure_ascii=False
.Manual QA steps
Risks
Rollback steps