Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-19170

Add backward compatibility for behavior change on multi line handling in automation operation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 6.0-HF28, 7.10-HF06, 8.2-SNAPSHOT
    • Fix Version/s: 6.0-HF29, 7.10-HF07, 8.2
    • Component/s: Automation
    • Tags:
    • Upgrade notes:
      Hide

      7.10 -> 8.2+
      When using properties of the form "key=value" for import, or in the Java Automation Client for example, the default behaviour for trailing spaces in 8 series has been inverted. Now trailing spaces around the value are not trimmed by default. For example "key= myValue" has a value " myValue" (note that it starts with a space). If you want to force back the previous behaviour, you should set the configuration property "nuxeo.automation.properties.value.trim" value to true. Otherwise, you have to be sure, that all your "key=value" inputs (in data files or source code) must be cleared of trailing spaces which are not actual part of the value.

      Show
      7.10 -> 8.2+ When using properties of the form "key=value" for import, or in the Java Automation Client for example, the default behaviour for trailing spaces in 8 series has been inverted. Now trailing spaces around the value are not trimmed by default. For example "key= myValue" has a value " myValue" (note that it starts with a space). If you want to force back the previous behaviour, you should set the configuration property "nuxeo.automation.properties.value.trim" value to true. Otherwise, you have to be sure, that all your "key=value" inputs (in data files or source code) must be cleared of trailing spaces which are not actual part of the value.
    • Sprint:
      NOS-14, NOS-15

      Description

      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.

        Attachments

          Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. NXP-14422 Fix escape handler in Automation Properties loader

          • Major - Major loss of function.
          • Resolved
          is required by

          Bug - A problem which impairs or prevents the functions of the product. NXP-19050 Java Automation Client must handle document update with multi-line string values

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. 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

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: