anchor.diff:  === Method Signatures
   
   '''
  -[[When-adding-a-new-paramemter-to-an-existing-method-a-default-value-SHOULD-be-used]]
  -[cols="2v,v"]
  -|===
  -| <<When-adding-a-new-paramemter-to-an-existing-method-a-default-value-SHOULD-be-used, Rule>>
  -| When adding a new paramemter to an existing method, a default value SHOULD be used
  +[[When-adding-a-new-parameter-to-an-existing-method-a-default-value-SHOULD-be-used]]
  +[cols="2v,v"]
  +|===
  +| <<When-adding-a-new-parameter-to-an-existing-method-a-default-value-SHOULD-be-used, Rule>>
  +| When adding a new parameter to an existing method, a default value SHOULD be used
   |===
   The purpose of this rule is to make it so that method signatures are backwards compatible.
   
  
positive.code: | Parameters to Ansible modules SHOULD use the Yaml dictionary format when the line length exceeds 120 characters
  |===
  
  Lines that are long quickly become a wall of text that isn't easily parsable. It is preferred to use the Ansible Yaml syntax to pass in parameters so that it's more clear what values are being passed for each paramemter.
  
  .Bad:
  [source,yaml]
  
negative.code: [[Ansible-Roles-SHOULD-be-named-like-technology_component_subcomponent]]
  [cols="2v,v"]
  |===
  | <<Ansible-Roles-SHOULD-be-named-like-technology_component_subcomponent, Rule>>
  | Ansible Roles SHOULD be named like technology_component[_subcomponent].
  |===
  
  