Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2205
Hey @pvillard31 I definitely where this is going. I agree that another
PR/JIRA can be issued for the more elaborate indication of processor-specific
variables in the EL. The only issue that I have with this as-is, is that if we
have processor that still indicates `.expressionLanguageSupported(true)`, in
the UI all that it says is "Expression Language Scope: NONE" and that believes
me to believe that Expression Language is not supported. I think if the
processor still indicates `true` instead of the Scope, that we still show in
the UI: "Expression Language Supported: true" or whatever it is that we show
currently.
The only other note, which is very minor, is that in the UI I would avoid
showing the Scope as NONE, VARIABLE_REGISTRY, FLOWFILE_ATTRIBUTES and instead
use human-friendly syntax: "Not Supported", "Variable Registry Only" and
"Variable Registry and FlowFile Attributes" - perhaps just update
ExpressionLanguageScope enum to contain a "description" or something and then
populate the DTO with that? Thoughts on that?
---
