-
Notifications
You must be signed in to change notification settings - Fork 614
Add 'True' string #2489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
samccann
wants to merge
1
commit into
devel
Choose a base branch
from
samccann-patch-1
base: devel
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+6
−6
Open
Add 'True' string #2489
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -112,14 +112,14 @@ While documentation examples focus on ``true/false`` to be compatible with ``ans | |
.. table:: | ||
:class: documentation-table | ||
|
||
=============================================================================================== ==================================================================== | ||
Valid values Description | ||
=============================================================================================== ==================================================================== | ||
``True`` , ``'true'`` , ``'t'`` , ``'yes'`` , ``'y'`` , ``'on'`` , ``'1'`` , ``1`` , ``1.0`` Truthy values | ||
========================================================================================================== ==================================================================== | ||
Valid values Description | ||
========================================================================================================== ==================================================================== | ||
``True`` , ``'True'``, ``'true'`` , ``'t'`` , ``'yes'`` , ``'y'`` , ``'on'`` , ``'1'`` , ``1`` , ``1.0`` Truthy values | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why add |
||
|
||
``False`` , ``'false'`` , ``'f'`` , ``'no'`` , ``'n'`` , ``'off'`` , ``'0'`` , ``0`` , ``0.0`` Falsy values | ||
``False`` , ``'false'`` , ``'f'`` , ``'no'`` , ``'n'`` , ``'off'`` , ``'0'`` , ``0`` , ``0.0`` Falsy values | ||
|
||
=============================================================================================== ==================================================================== | ||
========================================================================================================== ==================================================================== | ||
|
||
.. _list_variables: | ||
|
||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this table is being updated, it would be good to correct the introductory paragraph to mention that this only applies to
bool
module arguments.As currently written, this section makes it seem like these rules apply to variables in general, and to parsing of playbooks, inventory, etc. There may even be a better place in the documentation for this table, since it's not about variables, but module arguments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattclay getting back to this pr (finally). We don't talk a lot about module arguments in the docs that I can find. We do have https://docs.ansible.com/ansible/latest/module_plugin_guide/modules_intro.html where we could move this section to (Booleans in module arguments could be the new section title). What do you think?
And if I move it, is there any need to have any replacement text left here for how booleans are handled in variables in general?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's an acceptable location to move it to.
There's not really anything to document here about boolean variables, at least not for 2.19+, since Jinja native types are always used. There are boolean behaviors that could be documented elsewhere, but they're not specific to variables.