I am trying to add a nested list in my feature docs (for feature subsets)
example:
- ...
builtin_font (enabled by default) — Enable the built-in font (ProggyTiny, adds 35kb to the executable)builtin_elements (enabled by default) — Enable the built-in elements (Container, ProgressBar, etc.)
builtin_container — Enable only the Container component (which is essential for laying out other components)
- ...
However, it appears that implementing nested lists is currently not possible, even with the use of hacky workarounds.
I think adding a - (or */extra #) before the feature doc comment should add two spaces before the generated list entry, creating a nested list.
## Enable the built-in font (ProggyTiny, adds 35kb to the executable)
builtin_font = []
## Enable the built-in elements (`Container`, `ProgressBar`, etc.)
builtin_elements = ["builtin_container"]
## - Enable only the `Container` component (which is essential for laying out other components)
builtin_container = []
I am trying to add a nested list in my feature docs (for feature subsets)
example:
builtin_font(enabled by default) — Enable the built-in font (ProggyTiny, adds 35kb to the executable)builtin_elements(enabled by default) — Enable the built-in elements (Container, ProgressBar, etc.)builtin_container— Enable only the Container component (which is essential for laying out other components)However, it appears that implementing nested lists is currently not possible, even with the use of hacky workarounds.
I think adding a
-(or*/extra#) before the feature doc comment should add two spaces before the generated list entry, creating a nested list.