Subdirectives are not properly indented in the TOC

[p-pautov]

Feature Overview

Some Nginx modules define new configuration blocks with a bunch of directives there, e.g. http://nginx.org/en/docs/http/ngx_http_upstream_module.html (and there many more examples in N+).

It would be helpful to see such subdirectives indented in the TOC, i.e. instead of

Directives
    upstream
    server
    zone
    state
    ...

it should be

Directives
    upstream
        server
        zone
        state
        ...

Alternatives Considered

No response

Additional Context

No response

[pluknet]

Well, there's no such a notion like a sub-directive, neither in nginx nor nginx documentation.
Taking your example of the upstream module, upstream is a block directive defined in http context, and the rest directives documented there are defined in the upstream context. But this does not build a hierarchy like sub-directives.
Also, if imagine we have it, this seems to be limited to certain degenerate cases like upstream.
In contrary, the "context" xml tag provides the necessary info.

[p-pautov]

This does represent hierarchy, as "upstream" is the only context, in which these directives are allowed. And the idea is to simply make this hierarchy visible in the TOC, not to replace the "context" tag. This would be especially helpful for modules, which introduce both "sub-directives" in new block and directives in usual http/server/location contexts, such as

• https://nginx.org/en/docs/http/ngx_http_upstream_hc_module.html (the "match" block "sub-directives" currently lack proper documentation and only shown in examples)
• https://nginx.org/en/docs/http/ngx_http_acme_module.html
• https://nginx.org/en/docs/http/ngx_http_oidc_module.html
• ...