docs(linter): add backquotes where appropriate#15407
Conversation
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. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Pull Request Overview
This PR enhances documentation formatting across multiple ESLint rule files by adding backticks around code elements for improved readability and consistency.
- Adds backticks to function names, operators, and code expressions in documentation comments
- Improves visual distinction between code and descriptive text
- Maintains consistent formatting style across rule documentation
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| crates/oxc_linter/src/rules/eslint/use_isnan.rs | Adds backticks around isNaN(), Number.isNaN(), and NaN comparison expressions |
| crates/oxc_linter/src/rules/eslint/no_unsafe_optional_chaining.rs | Adds backticks around the optional chaining operator ?. |
| crates/oxc_linter/src/rules/eslint/no_extra_boolean_cast.rs | Adds backticks around !! operator and Boolean function name |
| crates/oxc_linter/src/rules/eslint/no_compare_neg_zero.rs | Adds backticks around -0, +0, code expressions, and Object.is() |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merge activity
|
Added backquotes where appropriate.
0bcbab5 to
57f0ce1
Compare
CodSpeed Performance ReportMerging #15407 will not alter performanceComparing Summary
Footnotes
|

Added backquotes where appropriate.