-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.0-HF28, 7.10-HF06, 8.2-SNAPSHOT
-
Component/s: Automation
-
Tags:
-
Upgrade notes:
-
Sprint:NOS-14, NOS-15
See change for NXP-19050: this introduces a behaviour change that should not be activated by default on maintenance branches.
Use a configuration property on a runtime contribution for documentation in explorer, named nuxeo.automation.properties.value.trim, set to true by default on master, and false for backport on 7.10 and 6.0.
–
7.10 -> 8.2+
On 7.10, the default value is "true" (values will be trimmed). This default value is in the code, but also in the default contribution properties-contrib.xml in nuxeo-automation-core (which is also used to automatically generate the documentation (in the explorer, if I recall correctly)).
In 8 series, the default value (in code and in default contribution) is "false". The spaces will not be trimmed by default.
The idea was to keep the current behaviour, but fix it in the FT, with possibility to keep former behaviour.
- depends on
-
NXP-14422 Fix escape handler in Automation Properties loader
-
- Resolved
-
- is required by
-
NXP-19050 Java Automation Client must handle document update with multi-line string values
-
- Resolved
-
-
NXS-3218 Switching back from 'YAML' editor to regular chain editor adds a space character after the '=' in operation 'Document.Update', which inserts the space character in the property's value
-
- Resolved
-