ArgumentStringHandler adds double quotes to an interpolated string using implicit conversion about nuke HOT 1 CLOSED

Hi @matkoch - please advise on what the intended usage for this kind of command setup - without using interpolation?

In the use case of a custom tool [PathVariable("my tool")] readily Tool MyTool with a MyTool.Invoke(cmd) We see in the Tool code implementation there in an implicit string cast of the arguments to a ArgumentStringHandler; but this behavior does not seem to be documented.

This seem to do more processing that has side effects, where we suspect it uses a code-generated implementation via the [[InterpolatedStringHandler] attribute that is opaque, like adding the extra quotes.

It would be good for those using Nuke to be able to understand this better...?

Our solution we to entirely build the command, with any interpolations, outside/before of the Tool.Invoke, and pass that in.

The implicit cast is not obvious unless ones IDE highlights them! This means folks get lost in thinking it is an error in their interpolation etc. than what is happening under the covers.

The implicit frictions issues such as this cause, may have folks consider alternative build solutions.

from nuke.