-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation of configuration properties with type Map<String, NotAConfigGroup> #40335
Conversation
…g, NotAConfigGroup>
/cc @brunobat (micrometer), @ebullient (micrometer), @gsmet (elasticsearch), @loicmathieu (elasticsearch) |
320698c
to
ab91604
Compare
…property in dev services
…figuration properties
ab91604
to
32ee0a9
Compare
Status for workflow
|
Damn, Guillaume went on PTO before he had time to review this. I thought he of all people would be interested. @geoand maybe? :) |
It LGTM, but I not done any work around this area not have I followed discussions so I am hesitant to approve |
Bump @gsmet :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks interesting, let's merge, thanks!
Fixes #40332
Before the patch:
After the patch (without CSS, since I tested locally...):
Unfortunately, this PR needs to set the name of the map keys, which will break direct links to the relevant configuration properties in the docs. That's because anchors are generated from the displayed key, including the
"some-name"
parts... which IMO is a dubious choice. We should probably change that to use anchors generated from some display-independent reference to the key. But that will result in breaking even more links, and anyway won't solve our problem here (since existing links will still be using the old anchor that includes the old"some-name"
), so I won't do it in this PR.