You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The large table didn't handle large descriptions or default values very well.
Especially if the values were code blocks since they do not overflow.
This change introduces a helper directive that will provide a consistent
formatting from a list of configuration options. The reason we went with
custom directive approach is the formatting of the configuration options
can be changed at any time without needing to reformat each option
individually.
The input to the directive is a YAML format of:
```yaml
OPTION_NAME:
type: <type>
default: <default>
description: <description>
```
If `type`is not provided then `String` is used.
If `default` is not provided then `(no value)` is used.
`description` **must** be provided.
If the value of `default` or `description` contains any special
characters then a multi-line YAML block must be used.
```yaml
description: |
``inline code block``
```
The values of `type`, `default`, and `description` may contain
rST formatted text.
Co-authored-by: Kyle Verhoog <[email protected]>
(cherry picked from commit a0eb79a)
Co-authored-by: Brett Langdon <[email protected]>
0 commit comments