Build and Strip Path primitive should be polymorphic and work on array.

[PJM_Labview]

The title say it all.

The Build and Strip Path primitive should be able to operate on array of path and array of string.

PJM

[muks]

Yes,Yes Yes go for it!!!

[Technico]

It maybe seems trivial, but other combinations need to become possible as well...

--> single 'base path' and array of 'name or rel path' (e.g. multiple files in a single dir)

--> array of 'base path' and a single 'name or rel path' (e.g. same filename in multiple dirs)

[Petru_Tarabuta]

+1.

The improvement to the Strip Path node is perfectly clear due to the node having a single input, and should "just be implemented".

The improvement to the Build Path node is more nuanced due to the node having two inputs. I agree with the suggestions made by Technico above, which address inputting a scalar and a 1D array, and vice versa. However, what should happen if the two inputs contain 1D arrays of different sizes? For example, what should happen if the first input (base path) contains 3 elements and the second input (name or rel path) contains 10 elements? How about if the array sizes were reversed (10 elements and 3 elements)?

For completeness, should the nodes also support 2D arrays (or even 3D and higher-dimension arrays)?