Skip to content

Fix/literal output#1424

Merged
SGSSGene merged 2 commits intojbeder:masterfrom
SGSSGene:fix/literal_output
Apr 8, 2026
Merged

Fix/literal output#1424
SGSSGene merged 2 commits intojbeder:masterfrom
SGSSGene:fix/literal_output

Conversation

@SGSSGene
Copy link
Copy Markdown
Collaborator

fixes #1238

This fixes the unit tests for expecting '|-' in cases where a string literal does not end on a new line. (Unit tests now fail)
It adds a unit test which also tests for '|+' (This tests now also fails)

Finally, added the missing functionality to make the unit tests pass again.

SGSSGene added 2 commits April 8, 2026 09:33
The unit test only tested for the '|' literal indicator.
But in some cases it should have been '|-'. If a string does not end
with an '\n' it has to use '|-' to indicate that the trailing new line
is not part of the string.

Additionally, I also added a explicit test for '|+'.
log: fix literal string outputs 'chomping indicator' if required
@SGSSGene SGSSGene force-pushed the fix/literal_output branch from 40b3e9a to 939e231 Compare April 8, 2026 07:33
@SGSSGene SGSSGene merged commit 992d9c4 into jbeder:master Apr 8, 2026
43 checks passed
@SGSSGene SGSSGene deleted the fix/literal_output branch April 8, 2026 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

YAML::Literal when new line at the end, shoud be |+ and not |

1 participant