This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Change yes/no to true/false #101
Labels
standard-breaking-change
This change breaks backward compatibility
vote-draft
Change proposal to the Standard or to the governance procedures
This specification defines a YAML file which should use
yes
/no
is accepted in several places. However, the meaning ofyes
/no
is ambiguous in YAML. In YAML 1.1 and older these values represent booleans, but in YAML 1.2 they don’t, meaning they represent strings.I suggest to remove this ambiguity by changing them to unambigous booleans (
true
/false
) in the specification.The text was updated successfully, but these errors were encountered: