Escape non-ascii characters in json payloads. #40
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
Even if the content type indicates a valid unicode charset, Zendesk does like non-ascii characters that aren't escaped. PS 6.2 added the `-EscapeHanding` parameter to `ConvertTo-Json` which can be used.
RobFaie
force-pushed
the
encoding
branch
2 times, most recently
from
b8abd7f to
e3b3965
Compare
|
Windows 2016 / PS 5.1 is having some issues. I will take a look tomorrow. |
mderriey
approved these changes
Mar 30, 2020
This will fix failing tests on Windows 2016 / PS 5.1
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.
Even if the content type indicates a valid unicode charset, Zendesk does like non-ascii characters that aren't escaped.
PS 6.2 added the
-EscapeHandingparameter toConvertTo-Jsonwhich can be used.