-
Notifications
You must be signed in to change notification settings - Fork 927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any support for join/concat #90
Comments
@ericsciple this seems like a decent addition to the expression language. Unless we already have something that will satisfy their scenario? (See the link above.) |
/cc @RussKeldorph |
I briefly discussed with @vtbassmatt and understand the scenario better now. Makes sense. I'll discuss further with Matt, so we can nail down the details in a spec somewhere (not strictly yaml; the core expression functions are available in other parts of the system too) |
@ericsciple Thank you for considering to add this feature! Can't wait to have this in any form in the language and remove ugly workaround introduced by dotnet/coreclr#22173 |
@vtbassmatt @echesakovMSFT @sbomer @chcosta what do you think about this proposed behavior: Join function
Or would this behavior be better:
|
I like the second behavior for the right parameter. In this case, I can think about the function as the following two steps transformation:
|
Yeah, now that you mention it, the silent conversion to an empty string would be confusing. |
This will roll out with the m148 payload. |
Is there any support to have an append to array. I see the support here converts an array to a string with a delimiter. However, the use case I'm looking for is to append to an array. For example
|
Update: I've added to feature requests here https://developercommunity.visualstudio.com/t/Function-to-append-to-a-yaml-Array/10166131?space=21&q=function+to+add+to+yaml+array&entry=myfeedback |
Is it possible now to join the elements of sequence to a string?
where
result
would containfoo;bar
stringOne of possible scenarios for this could specifying MSBuild semicolon-separated property values using array syntax (instead of a very long string)
The text was updated successfully, but these errors were encountered: