Adds ability to force json or xml parsing during templating #1200
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.
When requesting HTTP endpoints not under your control, you could come across an endpoint that doesn't respond with the correct content-type header value. For example getting an xml body, but the header says it's text/plain. You could also get a json body and there is no content-type header.
With this PR, I add a way to force parsing as json or xml when templating.
For JSON it would be like this:
{{previous_request_name.response.body.asJson.$.data.id}}
For XML it would be like this:
{{previous_request_name.response.body.asXml.//data/@id}}