fix(jsdoc): parse tags after interval notation in descriptions

[camc314]

No description provided.

[camc314]

• fix(jsdoc): parse tags after interval notation in descriptions #20046 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of 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.

[Copilot]

Pull request overview

Fixes an edge case in the JSDoc parser where math interval notation like [min, max) in free-form descriptions could prevent subsequent @tag lines from being recognized, which in turn impacted jsdoc-related linter rules.

Changes:

• Reset square-bracket and parenthesis nesting state on newline during JSDoc parsing to avoid prose like [min, max) blocking later tag detection.
• Add a focused unit test in oxc_jsdoc verifying tags are still parsed after interval notation in descriptions.
• Add linter rule test cases ensuring require_param / require_returns behave correctly with that JSDoc shape.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
crates/oxc_jsdoc/src/parser/parse.rs	Resets brace_depth / square_brace_depth per line so interval/prose brackets don’t suppress later @tag parsing.
crates/oxc_jsdoc/src/parser/jsdoc.rs	Adds a unit test asserting tags parse correctly after [min, max) appears in description text.
crates/oxc_linter/src/rules/jsdoc/require_returns.rs	Adds a regression test ensuring @returns is still recognized when interval notation appears in description.
crates/oxc_linter/src/rules/jsdoc/require_param.rs	Adds a regression test ensuring @param tags are still recognized when interval notation appears in description.

---

You can also share your feedback on Copilot code review. Take the survey.

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 52 skipped benchmarks¹

---

_{Comparing c/03-05-fix_jsdoc_parse_tags_after_interval_notation_in_descriptions (db35376) with main (6173e53)}

Footnotes

1. 52 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[leaysgur]

Merge activity

• Mar 23, 12:50 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 23, 12:53 AM UTC: leaysgur added this pull request to the Graphite merge queue.
• Mar 23, 12:56 AM UTC: Merged by the Graphite merge queue.