From 04821e952aa9bd7b8a8170aacf35d6711a1b579e Mon Sep 17 00:00:00 2001 From: Brant Evans Date: Tue, 14 Jan 2025 16:52:36 -0700 Subject: [PATCH] Move octal example code next to octals definition --- src/ansiblelint/rules/yaml.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/ansiblelint/rules/yaml.md b/src/ansiblelint/rules/yaml.md index 37bb3510c1..6a41376eaf 100644 --- a/src/ansiblelint/rules/yaml.md +++ b/src/ansiblelint/rules/yaml.md @@ -75,13 +75,6 @@ for it does check these. If for some reason, you do not want to follow our defaults, you can create a `.yamllint` file in your project and this will take precedence over our defaults. -## Additional Information for Multiline Strings - -Adhering to yaml[line-length] rule, for writing multiline strings we recommend -using Block Style Indicator: literal style indicated by a pipe (|) or folded -style indicated by a right angle bracket (>), instead of escaping the newlines -with backslashes. Reference [guide] for writing multiple line strings in yaml. - ## Problematic code ```yaml @@ -101,6 +94,13 @@ foo2: "0o777" # <-- Explicitly quoting octal is less risky. bar: ... # Correct comment indentation. ``` +## Additional Information for Multiline Strings + +Adhering to yaml[line-length] rule, for writing multiline strings we recommend +using Block Style Indicator: literal style indicated by a pipe (|) or folded +style indicated by a right angle bracket (>), instead of escaping the newlines +with backslashes. Reference [guide] for writing multiple line strings in yaml. + ## Yamllint configuration If you decide to add a custom yamllint config to your project, ansible-lint