fix(biome_html_parser): fix incorrect option name in HTML parser error message

[smorimoto]

Summary

The HTML parser error message for disabled text expressions incorrectly referred to the non-existent html.parser.textExpression option. This pull request fixes the error message to reference the correct html.parser.interpolation option, which is the actual configuration option for enabling interpolation parsing in HTML files.

Test Plan

Updated all related snapshot files. Existing tests will verify that the error message now displays the correct option name when users encounter text expressions with interpolation disabled.

Docs

No documentation changes required as this is a bug fix for an error message.
The corrected option name (html.parser.interpolation) already exists in the configuration schema.

[changeset-bot]

🦋 Changeset detected

Latest commit: e498d81

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

[dyc3]

Good catch, thank you!

Just fix the wording in the changeset :)

[coderabbitai]

Walkthrough

This change corrects a misnamed HTML parser option reference in an error message. The disabled_interpolation diagnostic hint text in the HTML parser was updated to reference the correct option name: html.parser.interpolation instead of the non-existent html.parser.textExpression. A corresponding changeset file was added to document this patch-level fix for the package.

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 (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The PR description is directly related to the changeset, providing a clear summary of the bug fix, the incorrect option name that was referenced, and the correct option that now replaces it. It includes relevant details about the test plan (snapshot updates) and documentation status, and avoids vague or generic language. The description is focused and on-topic throughout.
Title Check	✅ Passed	The pull request title "Fix incorrect option name in HTML parser error message" directly and clearly describes the main change in the changeset. The title specifically references the fix to an incorrect option name (from html.parser.textExpression to html.parser.interpolation) in the HTML parser's error message. It is concise, specific, and avoids vague terminology, making it immediately clear to a reviewer scanning the history what this PR addresses.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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