This repository has been archived by the owner on Jul 12, 2024. It is now read-only.
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.
Adds a new parameter to the body helper.
If it is set to true and the value is a primitive, the helper returns the stringified version of the value.
This fixes an issue where string values where not correctly escaped when being returned by a body helper. The reason for going with an extra parameter here is to 1. ensure backwards compatibility and 2. still enable user to use the unescaped values as the input to other helpers like
concat
.Parent issue
Closes mockoon/mockoon#397
(needs to be closed manually)
Technical implementation details
There is a third parameter for the body helper now. It is false by default and you can set the value by invoking it via
{{ body 'foo.bar' undefined true }}
. If the parameter is set totrue
, the value referenced by the path is processed byJSON.stringify
before it is returned. If parameter isfalse
, primitive values (i.e. null, integer, string, boolean) will not be processed byJSON.stringify
. However, objects and arrays will always be stringified, no matter which value the user passes for the parameter.