Project

General

Profile

Actions

Bug #17691

closed

Formating is lost for global param string looking like json

Added by François ARMAND over 4 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
13
Name check:
To do
Fix check:
To do
Regression:

Description

If we have a global parameter of type `string` which is a json, then when used in file content with ${node.properties[]}, then the formating is lost. That does not happen if the string is not json, or if the property is defined on node.

Global param:

On node:


Gives after enforce file content ==>

json_string_6_0
--
{"i'm not":"json"}
--

jsonStringOnNode
--
{
"that's" 
:
"not json but string" 
}
--

stringWithReturn
---
I'm a
multiline
string!
  with spaces
---

Files

clipboard-202006101050-ua8dv.png (3.6 KB) clipboard-202006101050-ua8dv.png François ARMAND, 2020-06-10 10:50
clipboard-202006101050-5junu.png (4.75 KB) clipboard-202006101050-5junu.png François ARMAND, 2020-06-10 10:50
clipboard-202006101052-fun7v.png (5.15 KB) clipboard-202006101052-fun7v.png François ARMAND, 2020-06-10 10:52
clipboard-202006101052-ijypu.png (6.23 KB) clipboard-202006101052-ijypu.png François ARMAND, 2020-06-10 10:52
clipboard-202006101053-a7vzm.png (6.38 KB) clipboard-202006101053-a7vzm.png François ARMAND, 2020-06-10 10:53
Actions

Also available in: Atom PDF