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
Yes, I agree that ideally the new lines should be present in the YAML.
Here's a related issue: #616 where we set max line length for snakeyaml (our YAML emitting library) to max, but it was rather a mitigation/workaround than a proper solution:
// Otherwise line breaks appear in places that create an incorrect YAML, e.g. in the middle of GitHub
// expressions.
.setWidth(Int.MAX_VALUE)
It was likely caused by a bug in snakeyaml. We track reporting this and other issues to the maintainer in #634. Once this is fixed, we can consider going back to having proper new lines in the emitted YAML.
What feature do you need?
If the
run
command, contains\n
it should be also a multiline string in the resulting yaml for better readability.Do you have an example usage?
Is there a workaround for not having this feature? If yes, please describe it.
no impact, just not as readable as multiline
The text was updated successfully, but these errors were encountered: