1. 13 6月, 2017 1 次提交
  2. 12 6月, 2017 3 次提交
  3. 08 6月, 2017 6 次提交
  4. 07 6月, 2017 5 次提交
  5. 06 6月, 2017 2 次提交
  6. 01 6月, 2017 1 次提交
  7. 31 5月, 2017 4 次提交
  8. 30 5月, 2017 11 次提交
  9. 29 5月, 2017 6 次提交
  10. 26 5月, 2017 1 次提交
    • C
      docstring directives: define more formal and strict format · 1719d983
      Cleber Rosa 提交于
      The format of the docstring directives has not been formally described
      so far.  Because at least two different features are built on that,
      and possibly more will come, it's a good idea to define a format.
      
      This introduces a stricter format, basically adding a number of
      requirements or rules.  To make the following description more
      consistent let's call the "🥑" part of the docstring directive
      "the marker" and what follows it the "content".
      
      1) One or more spaces are required between the "🥑" marker and
         the content.  The following is a valid docstring directive:
      
         "🥑 enable"
      
         While this is invalid:
      
         ":avocado:enable"
      
      2) A more limited set of characters are now allowed in the content,
         namely one from the following set: [a-zA-Z0-9_:,=].  The following
         is a valid docstring directive:
      
         "🥑 foo=bar,foz=baz:extra"
      
         While the following is invalid:
      
         "🥑 foo=bar!"
      
      3) The first character of the content must be alphanumeric, so the
         following is a valid docstring directive:
      
         "🥑 foo=bar"
      
         While the following is invalid:
      
         "🥑 =bar"
      
      4) An end of string (or end of line) is now required after the content
         (which itself may not contain white spaces).  The following is a
         valid docstring directive:
      
         "🥑 enable"
      
         While the following is invalid:
      
         "🥑 enable FOO"
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      1719d983