-
Notifications
You must be signed in to change notification settings - Fork 136
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
ytt formatting converts multi line strings to single line strings due to trailing spaces #847
Comments
I don't have any errant trailing spaces in my multi-line strings but recently also saw that ytt is now collapsing everything into a very long single line string, so it would be great to get this behaviour reverted or configurable. |
I'm able to successfully reproduce this issue. We will run our thoughts on this internally and set the priority accordingly. Meanwhile, if you are willing to contribute, we will be happy to review it on a priority basis. |
Also, could you please let us know if this is a blocking issue for your use case or you found any workaround? |
My current workaround is to run |
Signed-off-by: Fritz Duchardt <[email protected]>
@sethiyash Please have a look at my PR to fix the issue |
@fritzduchardt Thank you for reaching out with this issue and we appreciate the work you have done to fix it. |
What steps did you take:
I am running ytt on a config map with a multi line string and a trailing space after the colon in line 7, e.g.:
What happened:
Ytt unexpectedly converts the multi-line string to a single-line string:
What did you expect:
The multi-line string should be kept. The trailing white space could be removed.
Environment:
ytt --version
): 0.44.0/etc/os-release
): Ubuntu 20.04.4 LTSVote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: