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

Josef Zahner updated NIFI-15373:
--------------------------------
    Description: 
The Realtime property value syntax highlighting has been changed in NiFi > 
2.5.0. Let me provide two different examples from NiFi 2.7.1:
 # Parameters are not anymore checked at the time of writing whether they are 
valid, as soon as you enter “#{" and type, the word will be automatically 
always coloured.
!image-2025-12-19-07-09-24-878.png|width=293,height=184!
 # The same for NiFI Expression Language functions, as soon as you type 
"{{{}${your-var:}{{}}}}" the function will be coloured and not only if it's a 
valid function. In my example you can see that even \{{bla() }}has been 
coloured even thought it doesn't exists.
!image-2025-12-19-07-10-16-050.png|width=297,height=187!

This change/bug makes the endusers life really a lot more difficult as the live 
check is missing. You always have to press "Ok" and "Validate" or "Apply" to 
see whether the statement was correct or not. 

The answer from [~mcgilman] in Slack to this behaviour was the following: 
"{_}This is a consequence of {color:#de350b}*migrating to the latest version of 
Codemirror*{color} (see Jira Link below). Previously we were on a legacy 
version that needed to be migrated to a new major version. We are now on the 
latest major version and it has replaced syntax highlighting from a character 
streaming API to a lezer grammar that is compiled at build time. 
{color:#de350b}*Support for valid tokens at runtime would need to further 
evaluation.*{color}{_}{color:#de350b} *"*{color}

We would really appreciate if the behaviour on the newest NiFi versions would 
be the same as in earlier versions.

  was:
The Realtime property value syntax highlighting has been changed in NiFi > 
2.5.0. Let me provide two different examples from NiFi 2.7.1: # Parameters are 
not anymore checked at the time of writing whether they are valid, as soon as 
you enter “#{" and type, the word will be automatically always coloured.
!image-2025-12-19-07-09-24-878.png|width=293,height=184!
 # The same for NiFI Expression Language functions, as soon as you type 
"{{{}${your-var:}{}}}" the function will be coloured and not only if it's a 
valid function. In my example you can see that even {{bla() }}has been coloured 
even thought it doesn't exists.
!image-2025-12-19-07-10-16-050.png|width=297,height=187!

This change/bug makes the endusers life really a lot more difficult as the live 
check is missing. You always have to press "Ok" and "Validate" or "Apply" to 
see whether the statement was correct or not. 

The answer from [~mcgilman] in Slack to this behaviour was the following: 
"{_}This is a consequence of {color:#de350b}*migrating to the latest version of 
Codemirror*{color} (see Jira Link below). Previously we were on a legacy 
version that needed to be migrated to a new major version. We are now on the 
latest major version and it has replaced syntax highlighting from a character 
streaming API to a lezer grammar that is compiled at build time. 
{color:#de350b}*Support for valid tokens at runtime would need to further 
evaluation.*{color}{_}{color:#de350b} *"*{color}

We would really appreciate if the behaviour on the newest NiFi versions would 
be the same as in earlier versions.


> Realtime Syntax HIghlighting Behavior has changed in NiFi 2.6.0
> ---------------------------------------------------------------
>
>                 Key: NIFI-15373
>                 URL: https://issues.apache.org/jira/browse/NIFI-15373
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 2.6.0, 2.7.0, 2.7.1, 2.7.2
>            Reporter: Josef Zahner
>            Priority: Major
>         Attachments: image-2025-12-19-07-09-24-878.png, 
> image-2025-12-19-07-10-16-050.png
>
>
> The Realtime property value syntax highlighting has been changed in NiFi > 
> 2.5.0. Let me provide two different examples from NiFi 2.7.1:
>  # Parameters are not anymore checked at the time of writing whether they are 
> valid, as soon as you enter “#{" and type, the word will be automatically 
> always coloured.
> !image-2025-12-19-07-09-24-878.png|width=293,height=184!
>  # The same for NiFI Expression Language functions, as soon as you type 
> "{{{}${your-var:}{{}}}}" the function will be coloured and not only if it's a 
> valid function. In my example you can see that even \{{bla() }}has been 
> coloured even thought it doesn't exists.
> !image-2025-12-19-07-10-16-050.png|width=297,height=187!
> This change/bug makes the endusers life really a lot more difficult as the 
> live check is missing. You always have to press "Ok" and "Validate" or 
> "Apply" to see whether the statement was correct or not. 
> The answer from [~mcgilman] in Slack to this behaviour was the following: 
> "{_}This is a consequence of {color:#de350b}*migrating to the latest version 
> of Codemirror*{color} (see Jira Link below). Previously we were on a legacy 
> version that needed to be migrated to a new major version. We are now on the 
> latest major version and it has replaced syntax highlighting from a character 
> streaming API to a lezer grammar that is compiled at build time. 
> {color:#de350b}*Support for valid tokens at runtime would need to further 
> evaluation.*{color}{_}{color:#de350b} *"*{color}
> We would really appreciate if the behaviour on the newest NiFi versions would 
> be the same as in earlier versions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to