Thank you, Holden!
Yes, having everything live in the ConfigEntry is attractive.
The main reason I proposed an alternative where the groups are defined in YAML
is that if the config groups are defined in ConfigEntry, then altering the
groupings – which is relevant only to the display of config
I think this is a good idea. I like having everything in one source of
truth rather than two (so option 1 sounds like a good idea); but that’s
just my opinion. I'd be happy to help with reviews though.
On Wed, Feb 21, 2024 at 6:37 AM Nicholas Chammas
wrote:
> I know config documentation is not
I know config documentation is not the most exciting thing. If there is
anything I can do to make this as easy as possible for a committer to shepherd,
I’m all ears!
> On Feb 14, 2024, at 8:53 PM, Nicholas Chammas
> wrote:
>
> I’m interested in automating our config documentation and need
I’m interested in automating our config documentation and need input from a
committer who is interested in shepherding this work.
We have around 60 tables of configs across our documentation. Here’s a typical
example.
