clearml-server/server/schema/services
2020-06-01 13:07:35 +03:00
..
_api_defaults.conf Initial commit 2019-06-11 00:24:35 +03:00
_common.conf Initial commit 2019-06-11 00:24:35 +03:00
auth.conf Add API version 2.4 with new trains-server capabilities including DevOps and scheduling 2019-10-25 15:36:58 +03:00
events.conf Fix task can't be cloned if input model was deleted 2020-06-01 12:23:29 +03:00
models.conf Support filtering users by activity in projects 2020-06-01 11:55:40 +03:00
organization.conf Add organization.get_tags to obtain the set of all used task, model, queue and project tags 2020-06-01 13:00:35 +03:00
projects.conf Add API version 2.4 with new trains-server capabilities including DevOps and scheduling 2019-10-25 15:36:58 +03:00
queues.conf Add API version 2.4 with new trains-server capabilities including DevOps and scheduling 2019-10-25 15:36:58 +03:00
README.md Initial commit 2019-06-11 00:24:35 +03:00
server.conf Add server uid to server.info response in API v2.8 2020-06-01 13:01:31 +03:00
tasks.conf Add clear_all flag to tasks.reset 2020-06-01 13:07:35 +03:00
users.conf Support filtering users by activity in projects 2020-06-01 11:55:40 +03:00
workers.conf Add API version 2.4 with new trains-server capabilities including DevOps and scheduling 2019-10-25 15:36:58 +03:00

Writing descriptions

There are two options for writing parameters descriptions. Mixing between the two will result in output which is not Sphinx friendly. Whatever you choose, lines are subject to wrapping.

  • non-strict whitespace - Break the string however you like. Newlines and sequences of tabs/spaces are replaced by one space. Example:
    get_all {
        "1.5" {
            description: """This will all appear
            as one long
            sentence.
            Break lines wherever you
            like.
            """
        }
    }
    
    Becomes:
    class GetAllRequest(...):
        """
        This will all appear as one long sentence. Break lines wherever you
        like.
        """
    
  • strict whitespace - Single newlines will be replaced by spaces. Double newlines become a single newline WITH INDENTATION PRESERVED, so if uniform indentation is requried for all lines you MUST start new lines at the first column. Example:
    get_all {
        "1.5" {
            description: """
    Some general sentence.
    
    - separate lines must have double newlines between them
    
    - must begin at first column even though the "description" key is indented
    
    - you can use single newlines, the lines will be
      joined
    
        -- sub bullet: this line's leading spaces are preserved
    """
        }
    }
    
    Becomes:
    class GetAllRequest(...):
        """
        Some general sentence.
        - separate lines must have double newlines between them
        - must begin at first column even though the "description" key is indented
        - you can use single newlines, the lines will be joined
            -- sub bullet: this line's leading spaces are preserved
        """