crates/biome_analyze/CONTRIBUTING.md (1)

1214-1215: Wording tweak for clarity (single-file phrasing).

“individual files” reads a bit clunky. Suggest “single‑file examples” and “enable type inference”.

-  This is also useful to trigger type inference even for examples that only consist of individual files.
+  This also helps enable type inference for single‑file examples.

crates/biome_js_analyze/src/lint/nursery/no_misused_promises.rs (2)

31-64: Prefer TypeScript code fences for a TS-only rule.

This rule declares language: "ts" and relies on types. Using ts fences across these invalid examples makes type inference deterministic and avoids JS-mode edge cases.

-/// ```js,expect_diagnostic,file=promise-in-condition.js
+/// ```ts,expect_diagnostic,file=promise-in-condition.ts
@@
-/// ```js,expect_diagnostic,file=promise-in-ternary-condition.js
+/// ```ts,expect_diagnostic,file=promise-in-ternary-condition.ts
@@
-/// ```js,expect_diagnostic,file=promise-in-filter.js
+/// ```ts,expect_diagnostic,file=promise-in-filter.ts
@@
-/// ```js,expect_diagnostic,file=promise-while-condition.js
+/// ```ts,expect_diagnostic,file=promise-while-condition.ts
@@
-/// ```js,expect_diagnostic,file=spread-promise.js
+/// ```ts,expect_diagnostic,file=spread-promise.ts
@@
-/// ```js,expect_diagnostic,file=promise-in-forEach.js
+/// ```ts,expect_diagnostic,file=promise-in-forEach.ts

---

67-82: Valid block: consistent and comprehensive.

Using a single file=valid-promises.js block is tidy and keeps the harness fast. If you adopt TS fences above, consider aligning this to valid-promises.ts for consistency.

crates/biome_js_analyze/src/lint/nursery/no_floating_promises.rs (2)

55-58: Minor polish: make the Promise.all example unambiguously a statement.

A trailing semicolon avoids accidental continuation in concatenated snippets.

-/// Promise.all([p1, p2, p3])
+/// Promise.all([p1, p2, p3]);

---

116-152: Valid examples look good; consider declaring p1/p2/p3 to aid type inference.

Not required for this rule, but adding trivial declarations makes the snippet self‑contained.

 /// ```ts,file=valid-examples.ts
+/// const p1: Promise<unknown> = Promise.resolve(1);
+/// const p2: Promise<unknown> = Promise.resolve(2);
+/// const p3: Promise<unknown> = Promise.resolve(3);
 /// async function returnsPromise(): Promise<string> {

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-09-05T06:39:46.267Z
Learning: Applies to crates/biome_analyze/crates/**/lib/src/**/*.rs : Use `file=<path>` in doc code blocks for multi-file test snippets when cross-file analysis is needed

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-09-05T06:39:46.267Z
Learning: Applies to crates/biome_analyze/crates/**/lib/src/**/*.rs : Rule documentation (Rust doc comments) must start with a single-line summary, include `## Examples` with `### Invalid` first then `### Valid`, and document options under `## Options`

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-09-05T06:39:46.267Z
Learning: Applies to crates/biome_analyze/crates/**/lib/src/**/*.rs : Code blocks in rule docs must specify a language; invalid examples use `,expect_diagnostic` and must emit exactly one diagnostic; use `ignore` sparingly

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-09-05T06:39:46.267Z
Learning: Applies to crates/biome_analyze/crates/**/lib/src/**/*.rs : When showing rule-specific configuration in docs, use `json`/`jsonc` with `,options` (or `,full_options` for full biome.json); follow the modifier order `<lang>[,expect_diagnostic][,(options|full_options|use_options)][,ignore][,file=path]`