Rewrite best practices to encourage tabs

While still allowing spaces, and just promoting consistency. Fixes #73
galaxy-iuc · Nov 14, 2022 · 9c17c4c · peterjc · Nov 14, 2022 · peterjc
1 parent a26656b
commit 9c17c4c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/best_practices/integration_checklist.rst b/docs/best_practices/integration_checklist.rst
@@ -38,7 +38,7 @@ Creating the Tool Wrapper (XML File)
     - Provide the comment-only ``tool_data_table_conf.xml.sample`` file
 - Check that the XML elements and parameters attributes are in the `Order specified in the Best Practices <http://galaxy-iuc-standards.readthedocs.io/en/latest/best_practices/tool_xml.html#coding-style>`__.
 - If you have a collection of related tools you can try to avoid duplicating XML by using a `Macros XML file <http://planemo.readthedocs.io/en/latest/writing_standalone.html#macros>`__       
-- Use 4 spaces for indentation.
+- Use tabs for indentation. (4 space indentation is permitted as long as the author is consistent)
 
 Testing Your Tool
 -----------------

diff --git a/docs/best_practices/tool_xml.rst b/docs/best_practices/tool_xml.rst
@@ -315,7 +315,7 @@ TODO
 Coding Style
 ------------
 
-* 4 spaces indent
+* Tabs for indentation (spaces permitted if consistent.)
 * Order of XML elements:
 
   * `description`_