[PR #2408/d8c36a01 backport][stable-2.18] Fix YAML syntax, adjust more code block languages #2419
Conversation
This file contains hidden or 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
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
* Fix broken YAML, or adjust code block type. * Normalize code block type. (cherry picked from commit d8c36a0)
felixfontein
deleted the
patchback/backports/stable-2.18/d8c36a014f305acafed82cc3c2d699053f22a9c9/pr-2408
branch
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.
This is a backport of PR #2408 as merged into devel (d8c36a0).
I went through the problems mentioned by #2385 after #2382 got merged.
Quite a few places were things like
...in YAML to indicate "some more content here". I usually replaced it by# ....Another large set (especially in the filters documentation) was something that was a Jinja template, but not really YAML. I usually tagged them as
jinjainstead. Everything that is taggedyaml+jinjashould be syntactially valid YAML. That also means I had to change back #2382 (comment) since this Jinja template cannot be made valid YAML, due to the value fordependencies, which must be a dictionary, and cannot be (in Ansible-style) a YAML string that evaluates to a dictionary.