docs(lint/html): fix some html rule docs that mess up markdown rendering on the website

[dyc3]

Summary

Test Plan

Docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: cab5edf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[coderabbitai]

Walkthrough

Documentation formatting updates across two Vue linting rule files. The changes involve wrapping code example snippets in backticks within doc comments for improved formatting consistency. No functional logic, control flow, or error handling modifications are present in either file.

Suggested labels

A-Linter, L-HTML

Suggested reviewers

• ematipico

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description contains only the standard PR template with placeholders and no actual details about the changes, motivation, or testing.	Fill in the Summary, Test Plan, and Docs sections with meaningful information about the documentation fixes and how they were validated.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: fixing HTML rule documentation formatting to resolve markdown rendering issues on the website.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dyc3/fix-html-docs

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2dd38cf and cab5edf.

📒 Files selected for processing (2)

• crates/biome_html_analyze/src/lint/nursery/no_vue_v_if_with_v_for.rs (1 hunks)
• crates/biome_html_analyze/src/lint/nursery/use_vue_valid_v_on.rs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Documentation
• GitHub Check: Test (depot-ubuntu-24.04-arm-16)
• GitHub Check: End-to-end tests
• GitHub Check: Test (depot-windows-2022-16)
• GitHub Check: Lint project (depot-ubuntu-24.04-arm-16)
• GitHub Check: Check Dependencies
• GitHub Check: Lint project (depot-windows-2022)
• GitHub Check: autofix
• GitHub Check: Test Node.js API

🔇 Additional comments (2)

crates/biome_html_analyze/src/lint/nursery/no_vue_v_if_with_v_for.rs (1)

13-14: Documentation formatting for inline code examples looks good.

Wrapping the inline Vue/HTML snippets in backticks will render them properly as code on the website instead of being interpreted as plain text. Clean and consistent.

crates/biome_html_analyze/src/lint/nursery/use_vue_valid_v_on.rs (1)

14-16: Documentation formatting improvements approved.

The inline HTML/Vue directive examples are now properly marked as code with backticks, which will render correctly on the website. Consistent with the parallel changes in the other file.

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.}