[Flow] UI improvement on editable outputs that shouldn't be deleted and consistency between this.

[fietser28]

Is your feature request related to a problem? Please describe.
This is just a consistency/UI improvement:
The UI currently allows you to delete or rename certain outputs of actions that should not be renamed or deleted. Deleting or renaming will trigger an error during execution and is never a valid use case (imho). Examples actions are: Eval JS, CSVParse and JSONParse. I'm also not sure if this is currently consistent between all actions (Eval and Watch don't allow you to edit/delete the output type).

Describe the solution you'd like
Disable the rename and delete buttons for these outputs.
All actions should have consistent implementation.

Describe alternatives you've considered
Hide these type of outputs in the custom outputs list, but in that case the output type can't be set by the users.
Alternative would be to add a fixed UI item to choose the output type under the specific group of the action.

[mvladic]

These action allows output editing so you can change output type, from example by default JSONParse will output 'json' but you can change it to your structure type. But, I agree we should do something about this problem when you change the name or completely delete it - we could at least report this as an error in Checks tab.

[fietser28]

Error in the Checks tab is a good idea.

How about the alternative: add a fixed UI item to choose the output type under the specific group of the action?

I'm also wondering if the 'Eval' result output should have a user definable type?

[mvladic]

How about the alternative: add a fixed UI item to choose the output type under the specific group of the action?

Yes, it makes sense.

I'm also wondering if the 'Eval' result output should have a user definable type?

Actually, Eval could deduce (in most cases) type from the Expression. Studio is actually doing that internally but we don't use that information for this particular action and output of Eval is always set to any. But, it could be of this deduced type. Which will give you more information in Checks tab: for example, if you connected Eval result to the input of different type that we deduced from Expression.