clearml-server/apiserver/schema/services
2022-07-08 17:45:33 +03:00
..
_api_defaults.conf Rename server to apiserver 2021-01-05 16:22:34 +02:00
_common.conf Add support for credentials label 2022-02-13 19:59:58 +02:00
auth.conf Add auth.edit_credentials 2022-05-17 16:08:12 +03:00
debug.conf Rename server to apiserver 2021-01-05 16:22:34 +02:00
events.conf Add support for navigate_current_metric in events.get_debug_image_sample 2022-07-08 17:31:44 +03:00
login.conf Add missing login.logout endpoint 2021-05-11 16:12:27 +03:00
models.conf Add support for model statistics 2022-07-08 17:39:41 +03:00
organization.conf Add support for Dataset projects 2022-07-08 17:45:03 +03:00
pipelines.conf Add pipelines support 2022-03-15 16:28:59 +02:00
projects.conf Add support for Dataset projects 2022-07-08 17:45:03 +03:00
queues.conf Support max_task_entries option in queues.get_by_id/get_all 2022-07-08 17:42:20 +03:00
README.md Rename server to apiserver 2021-01-05 16:22:34 +02:00
server.conf Rename migration script 2021-01-05 18:09:34 +02:00
tasks.conf Support publish option in tasks.completed 2022-07-08 17:40:43 +03:00
users.conf Return getting_started_info in users.get_current_user 2022-07-08 17:45:33 +03:00
workers.conf Support workers filtering with tags 2022-07-08 17:37:33 +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
        """