feat(js_analyze): implement noTernary

[Netail]

Summary

Implement Eslint's noTernary

Closes #8200

Test Plan

Docs

[changeset-bot]

🦋 Changeset detected

Latest commit: 4f2bf6d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
@biomejs/biome	Patch
@biomejs/cli-win32-x64	Patch
@biomejs/cli-win32-arm64	Patch
@biomejs/cli-darwin-x64	Patch
@biomejs/cli-darwin-arm64	Patch
@biomejs/cli-linux-x64	Patch
@biomejs/cli-linux-arm64	Patch
@biomejs/cli-linux-x64-musl	Patch
@biomejs/cli-linux-arm64-musl	Patch
@biomejs/wasm-web	Patch
@biomejs/wasm-bundler	Patch
@biomejs/wasm-nodejs	Patch
@biomejs/backend-jsonrpc	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This pull request introduces a new nursery lint rule noTernary to the Biome JavaScript linter that disallows the use of the ternary operator. The change includes the rule implementation targeting conditional expressions, configuration options support, test coverage with both valid and invalid test cases demonstrating the rule's behaviour, and the necessary module exports.

Suggested labels

A-Project, A-Linter, L-JavaScript, A-Diagnostic

Suggested reviewers

• dyc3
• ematipico

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description directly references the ESLint rule being ported and links to the corresponding GitHub issue, clearly relating to the changeset.
Linked Issues check	✅ Passed	The PR successfully implements the noTernary rule as requested in issue #8200, with proper rule declaration, test coverage, and options configuration [#8200].
Out of Scope Changes check	✅ Passed	All changes are directly related to implementing the noTernary rule; no out-of-scope modifications detected.
Title check	✅ Passed	The title 'feat(js_analyze): implement noTernary' accurately summarises the main change—adding a new linting rule to disallow ternary operators in JavaScript code.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codspeed-hq]

CodSpeed Performance Report

Merging #8201 will not alter performance

_{Comparing Netail:feat/no-ternary (4f2bf6d) with main (23f7855)¹}

Summary

✅ 58 untouched
⏩ 95 skipped²

Footnotes

1. No successful run was found on main (c738a1c) during the generation of this report, so 23f7855 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 95 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. ↩

[ematipico]

Easy :)