Remove escape characters from Jenkins response body #295
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
itskingori
force-pushed
the
fix_jenkins_response_issue
branch
from
0702743 to
371b721
Compare
zacblazic
force-pushed
the
fix_jenkins_response_issue
branch
from
371b721 to
202630a
Compare
|
please add a test too |
|
ah yes, saw the example ... just put that into a test and this should be goo to go :) |
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.
To fix an issue with the
\echaracter which seems like an issue withJSON.parseso figured this is a simpler solution (we can discuss alternatives i.e. if we should change toOj... there).Closes #294.