clearml-server/apiserver/schema/services
2024-01-10 15:12:56 +02:00
..
_api_defaults.conf
_common.conf Add filters parameter for passing user defined list filters for all get_all_ex apis 2023-11-17 09:36:58 +02:00
_events_common.conf Add task names to events.get_single_value_metrics endpoint response 2023-07-26 18:50:53 +03:00
_tasks_common.conf Fix schema for swagger compatibility 2023-11-17 09:39:52 +02:00
auth.conf Add auth.edit_credentials 2022-05-17 16:08:12 +03:00
debug.conf
events.conf Fix model_metrics parameter name in get_multi_task_metrics schema 2024-01-10 15:12:56 +02:00
login.conf Optimize endpoints that do not require authorization by not validating JWT token 2023-11-17 09:45:22 +02:00
models.conf Update API to 2.27 2023-11-17 09:40:34 +02:00
organization.conf Fix schema for swagger compatibility 2023-11-17 09:39:52 +02:00
pipelines.conf Fix schema for swagger compatibility 2023-11-17 09:39:52 +02:00
projects.conf Support filtering by task or model ids in projects.get_unique_metric_variants 2024-01-10 15:06:21 +02:00
queues.conf Update API to 2.27 2023-11-17 09:40:34 +02:00
README.md
reports.conf Update API to 2.27 2023-11-17 09:40:34 +02:00
server.conf Rename migration script 2021-01-05 18:09:34 +02:00
tasks.conf Update API to 2.27 2023-11-17 09:40:34 +02:00
users.conf Add max_download_items to users.get_current_user endpoint response 2023-07-26 18:45:42 +03:00
workers.conf Update API version to 2.26 2023-07-26 18:44:20 +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
        """