Actions
Bug #17674
closed
Global parameter "string" doesn't escape json
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
If you chose "string" for a global parameter and the value is json, it is not correctly escaped.
It does not seems blocking (just grave) since you can still print the json string, or add double quote to get a formatted json - but in that case, you also get the quote printed.
So, tu sum up, this is whant you get, and what we would like to have (in file enforce content):
| global parameter name | global parameter value | in ldap | type in param | type in node | in file enforce content directive | printed in file | comment |
|---|---|---|---|---|---|---|---|
| p1 | { "foo":"bar" } |
{"foo":"bar"} | string | json | ${node.properties[p1] | {"foo":"bar"} | same as if the type was string but formating is lost, override will work like for json |
| p2 | {"foo":"bar"} | {"foo":"bar"} | json | json | ${node.properties[p2] | {"foo":"bar"} | as expected |
| p3 | "{ "foo":"bar" }" |
"\{\"foo\":\"bar\"\}" | string | string | ${node.properties[p3] | "{ "foo":"bar" }" |
as expected. Formatting kept, but " remains |
Updated by 
Updated by
Actions