Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
lib/options/showOption: fix quoting of attr-names that are not identifiers #194035
lib/options/showOption: fix quoting of attr-names that are not identifiers #194035
Changes from all commits
ac48f07
6396482
2480532
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This changes the identifiers, breaking inbound links. Could you remove the quotes instead of replacing them with underscores?
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.
Shouldn't that throw an error if
<xref linkend="" />
points to an unknown location?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.
Then that would have been a problem before.
You'd have to define
options."" = mkOption ...
at the top level, which I don't think is something we have to worry about.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.
Yes. But considering that I can build the manual locally, doesn't that mean that there are no breaking links?
Even though it's just a theoretical problem, having e.g.
settings."foo.bar"
andsettings.foo.bar
defined would cause a conflict when removing the quotes, that's why I kept them.Or am I misunderstanding your point? :)
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.
ping @roberth
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.
I was more concerned about links from the web to the manual. Passing the internal validation will not detect such broken links.
It does appear that the impact is quite limited:
(
{+_+}
is git word diff syntax for "add underscore")opt-services.sourcehut.settings.{+_+}sr.ht{+_+}.owner-name
opt-services.listmonk.database.settings.{+_+}app.notify_emails{+_+}
opt-services.listmonk.database.settings.{+_+}bounce.mailboxes{+_+}
opt-services.listmonk.database.settings.{+_+}privacy.domain_blocklist{+_+}
opt-services.listmonk.database.settings.{+_+}privacy.exportable{+_+}
opt-services.xserver.windowManager.{+_+}2bwm{+_+}.enable
This seems like a small price to pay for a simpler and more injective id generating function.