DX-2133: add stringifyBody parameter to context.call and context.invoke #131
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.
By default, all bodies passed to context.call and context.invoke are stringified. This means, if you are calling an endpoint which expects specific strings (imagine
"coin=BTC"
) in the body, the string you passed will be stringified and become'"coin=BTC"'
and the API you are calling will return 400.Since we can't change the default behavior which could break many other workflows, we add a parameter to disable the stringify operation. If stringify is disabled, body needs to be string.
In a future major release we may:
in both methods, stringifyBody is true by default. I also added tests to both method to check for different behaviors.