Issue 1367: Reformat YAML to Always Use Literal Block for Query Text #1370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
😱 [INFO][root]: ignoring file dependabot.yml |
arielkr256
added
bug
arielkr256
approved these changes
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Background
#1367 raised the problem that using a folded block (
>) when denoting SQL code in our YAML files can cause issues for some YAML parsers, since>allows the parser to insert line breaks where it find convenient, potentially breaking certain parts of the query. By using the literal block|, we ensure parsers maintain the current formatting of the SQL code.Changes
>block style to literal|block style.Testing