You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Providing nested list to String.Concat controls the behaviour of subsequent lists. List levels have no influence
Also input names are confusing 'string0' would be clearer if it were 'list0', etc.
What did you expect to see?
I would expect that using levels would flatten nested lists and that each concatenation is independent of the previous input
I note that the code uses the .Net String.Concat method - so the issue is likely with the implementation by MicroSoft?
What did you see instead?
See above
I would like to see concatenation is independent of the previous one and list levels are honoured
What packages or external references (if any) were used?
None
Stack Trace
N/A
Details
N/A
The text was updated successfully, but these errors were encountered:
Thank you for submitting the issue to us. We are sorry to see you get stuck with your workflow. While waiting for our team member to respond, please feel free to browse our forum at https://forum.dynamobim.com/ for more Dynamo related information.
Dynamo Version
v3.2.2
Host
Dynamo Sandbox
Operating System
Windows 11 Enterprise 23H2
What did you do?
Providing nested list to String.Concat controls the behaviour of subsequent lists. List levels have no influence
Also input names are confusing 'string0' would be clearer if it were 'list0', etc.
What did you expect to see?
I would expect that using levels would flatten nested lists and that each concatenation is independent of the previous input
I note that the code uses the .Net String.Concat method - so the issue is likely with the implementation by MicroSoft?
What did you see instead?
See above
I would like to see concatenation is independent of the previous one and list levels are honoured
What packages or external references (if any) were used?
None
Stack Trace
N/A
Details
N/A
The text was updated successfully, but these errors were encountered: