summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAnkur H. Singh <49074231+sankur-codes@users.noreply.github.com>2021-10-05 16:43:49 +0530
committerGitHub <noreply@github.com>2021-10-05 04:13:49 -0700
commit000ae00cfd2dcb55c26362b75f94870ab02352ff (patch)
treea0b31cf7fd3198869856026a6fbaced288480dd1
parent19fce0527a106cc4bb00df1a36ca58fcd7eb58ee (diff)
downloadansible-000ae00cfd2dcb55c26362b75f94870ab02352ff.tar.gz
Docs: Clarify adding newlines in YAML folded block scalar (#75875)
* Removed translatable words from code blocks ##### SUMMARY Removed translatable words from codeblocks as per #59449 ##### ISSUE TYPE - Docs Pull Request +label: docsite_pr * Maintaining intend as well as clearity * Preserving "save_as" as the key * showing equivalence and keeping same context
-rw-r--r--docs/docsite/rst/reference_appendices/YAMLSyntax.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/docsite/rst/reference_appendices/YAMLSyntax.rst b/docs/docsite/rst/reference_appendices/YAMLSyntax.rst
index fe1f06ee1d..5cdd2f10b5 100644
--- a/docs/docsite/rst/reference_appendices/YAMLSyntax.rst
+++ b/docs/docsite/rst/reference_appendices/YAMLSyntax.rst
@@ -107,7 +107,10 @@ While in the above ``>`` example all newlines are folded into spaces, there are
d
e
f
- same_as: "a b\nc d\n e\nf\n"
+
+Alternatively, it can be enforced by including newline ``\n`` characters::
+
+ fold_same_newlines: "a b\nc d\n e\nf\n"
Let's combine what we learned so far in an arbitrary YAML example.
This really has nothing to do with Ansible, but will give you a feel for the format::