fix(linter): respect --fix vs --fix-suggestions for tsgolint diagnostics

[camc314]

No description provided.

[camc314]

• fix(linter): respect --fix vs --fix-suggestions for tsgolint diagnostics #16462 👈 (View in Graphite)
• 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 Performance Report

Merging #16462 will not alter performance

_{Comparing c/12-03-fix_linter_respect_--fix_vs_--fix-suggestions_for_tsgolint_diagnostics (fd0b7cc) with main (9001234)}

Summary

✅ 4 untouched
⏩ 41 skipped¹

Footnotes

1. 41 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. ↩

[Sysix]

Is this really needed? I thought with oxc-project/tsgolint#317 the payload only includes what is requested. So without --fix there is no val.fixes