[jira] [Updated] (NIFI-9336) When configuring component properties, UI should flag/make obvious when there is whitespace

["Mark Payne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-9336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-9336:
-----------------------------
    Description: 
It is a very common problem that users will copy & paste values into the property configuration for a processor/controller service/etc. And this often results in unwanted white space at the beginning or end of the property value (especially the end). This can have very confusing results, like indicating that a hostname cannot be found or that credentials are invalid, etc. but the issue is not obvious when an error message looks like:

{{No route to host: 1.1.1.1}}

At the same time, we cannot simply have NiFi trim all property values, because sometimes white space is important. For example, Merge Content allows a header/footer/demarcator which may well intentionally include whitespace.

While we could add an indicator to Property Descriptors to address this issue, such as:
 {{.trimWhiteSpace(true)}}

it will be easy to forget adding that to the Property Descriptor, and if we default it to true, it would change behavior of many processors unexpectedly.

Since we cannot trim the values automatically, the UI should flag this when configuring property values, making it very clear that there is leading or trailing whitespace.

  was:
It is a very common problem that users will copy & paste values into the property configuration for a processor/controller service/etc. And this often results in unwanted white space at the beginning or end of the property value (especially the end). This can have very confusing results, like indicating that a hostname cannot be found or that credentials are invalid, etc. but the issue is not obvious when an error message looks like:
{{}}

{{No route to host: 1.1.1.1}}

At the same time, we cannot simply have NiFi trim all property values, because sometimes white space is important. For example, Merge Content allows a header/footer/demarcator which may well intentionally include whitespace.

While we could add an indicator to Property Descriptors to address this issue, such as:
{{.trimWhiteSpace(true)}}, it will be easy to forget adding that to the Property Descriptor, and if we default it to true, it would change behavior of many processors unexpectedly.

Since we cannot trim the values automatically, the UI should flag this when configuring property values, making it very clear that there is leading or trailing whitespace.


> When configuring component properties, UI should flag/make obvious when there is whitespace
> -------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9336
>                 URL: https://issues.apache.org/jira/browse/NIFI-9336
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Mark Payne
>            Priority: Major
>
> It is a very common problem that users will copy & paste values into the property configuration for a processor/controller service/etc. And this often results in unwanted white space at the beginning or end of the property value (especially the end). This can have very confusing results, like indicating that a hostname cannot be found or that credentials are invalid, etc. but the issue is not obvious when an error message looks like:
> {{No route to host: 1.1.1.1}}
> At the same time, we cannot simply have NiFi trim all property values, because sometimes white space is important. For example, Merge Content allows a header/footer/demarcator which may well intentionally include whitespace.
> While we could add an indicator to Property Descriptors to address this issue, such as:
>  {{.trimWhiteSpace(true)}}
> it will be easy to forget adding that to the Property Descriptor, and if we default it to true, it would change behavior of many processors unexpectedly.
> Since we cannot trim the values automatically, the UI should flag this when configuring property values, making it very clear that there is leading or trailing whitespace.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)