Update writeFiles function to handle newline characters more accurately #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Currently, the setup echo commands treat "\n" as literal strings instead of newlines, when we wanted them to be interpreted as newlines.
Fix
Add '-e' flag to the echo commands.
Fixture
Note
Improve echo logging to correctly interpret newline escapes and update fixtures to match.
writeFilesto chooseechoflags based on newline usage:echo.echo -e(with trailing) orecho -ne(without trailing).internal/test_helpers/fixtures/{ash,bash}/pipelines/passto reflectecho -efor multi-line setup writes.Written by Cursor Bugbot for commit f354218. This will update automatically on new commits. Configure here.