refactor(linter): add diagnostics_with_multiple_fixes to LintContext

[Sysix]

With something like that win forward_ref_uses_ref:

fn check_forward_ref_inner<'a>(
    exp: &Expression,
    call_expr: &CallExpression,
    ctx: &LintContext<'a>,
) {
    let (params, span) = match exp {
        Expression::ArrowFunctionExpression(f) => (&f.params, f.span),
        Expression::FunctionExpression(f) => (&f.params, f.span),
        _ => return,
    };
    if params.parameters_count() != 1 || params.rest.is_some() {
        return;
    }

    ctx.diagnostics_with_multiple_fixes(
        forward_ref_uses_ref_diagnostic(span),
        (
            FixKind::Suggestion,
            |fixer: RuleFixer<'_, 'a>| {
                fixer.replace_with(call_expr, exp).with_message("remove `forwardRef` wrapper")
            }
        ),
        (
            FixKind::Suggestion,
            |fixer: RuleFixer<'_, 'a>| {
                fixer.replace_with(call_expr, exp).with_message("add `ref` parameter")
            }
        ),
    );
}

I get in VSCode the setting 🥳

[Sysix]

• refactor(linter): add diagnostics_with_multiple_fixes to LintContext #11357 👈 (View in Graphite)
• refactor(linter): accept PossibleFixes instead of Fix for Messages #11295
• refactor(linter): use PossibleFixes instead of Option<Fix> #11284
• 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 hot fixes, skip the queue and merge this PR next

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.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11357 will create unknown performance changes

_{Comparing 05-28-refactor_linter_add_diagnostics_with_multiple_fixes_to_lintcontext_ (50ef691) with main (606bb34)}

Summary

🆕 38 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	codegen[RadixUIAdoptionSection.jsx]	N/A	132.1 µs	N/A
🆕	codegen[binder.ts]	N/A	4.8 ms	N/A
🆕	codegen[cal.com.tsx]	N/A	38.9 ms	N/A
🆕	codegen[react.development.js]	N/A	2.2 ms	N/A
🆕	formatter[RadixUIAdoptionSection.jsx]	N/A	299 µs	N/A
🆕	formatter[binder.ts]	N/A	18.9 ms	N/A
🆕	formatter[cal.com.tsx]	N/A	142.8 ms	N/A
🆕	formatter[react.development.js]	N/A	9.2 ms	N/A
🆕	lexer[RadixUIAdoptionSection.jsx]	N/A	21 µs	N/A
🆕	lexer[binder.ts]	N/A	929.2 µs	N/A
🆕	lexer[cal.com.tsx]	N/A	5.8 ms	N/A
🆕	lexer[react.development.js]	N/A	383.7 µs	N/A
🆕	linter[RadixUIAdoptionSection.jsx]	N/A	2.8 ms	N/A
🆕	linter[binder.ts]	N/A	148.5 ms	N/A
🆕	linter[cal.com.tsx]	N/A	1.3 s	N/A
🆕	linter[react.development.js]	N/A	54.4 ms	N/A
🆕	mangler[RadixUIAdoptionSection.jsx]	N/A	14.6 µs	N/A
🆕	mangler[binder.ts]	N/A	797.2 µs	N/A
🆕	mangler[cal.com.tsx]	N/A	2.7 ms	N/A
🆕	mangler[react.development.js]	N/A	282.9 µs	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[camc314]

Merge activity

• May 29, 2:00 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• May 29, 2:15 PM UTC: Sysix added this pull request to the Graphite merge queue.
• May 29, 2:18 PM UTC: Merged by the Graphite merge queue.