docs(linter): Improve the Options documentation for no-empty-function rule#14789
Conversation
… rule. Previously this wasn't following the same format as most other rules with options, now it is.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
There was a problem hiding this comment.
Pull Request Overview
Align the no-empty-function rule documentation with the standard “Options” format used by other rules, improving clarity and consistency.
- Replaces “Configuration” with structured “Options” section and an “allow” subsection including type/default.
- Updates the example to show a focused rule configuration snippet.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Connor Shea <connor.james.shea@gmail.com>
CodSpeed Performance ReportMerging #14789 will not alter performanceComparing Summary
Footnotes
|
Previously this wasn't following the same format as most other rules with options, now it is.
Related to #14743
I tried converting this to auto-gen docs, but I have no idea how to get that working without the compiler complaining, honestly.