fix(linter): Fix syntax error reporting in some output formatters.

[connorshea]

Add snapshot tests for all the formatters with this case to make sure we don't regress on this for any of them in the future.

Basically, we were being overly aggressive in the stripping of the rule ID from the message, which caused messages with colons in them (e.g. parser errors like Expected ;but found:``) to be truncated to just the character after the first colon.

We don't actually need to do this anymore, as the diagnostic.to_string() method doesn't include the rule ID (if it ever did), so we can just use the full string as the message without any additional parsing.

Generated with Claude Code.

Fixes #19588.

[connorshea]

Confirmed that this impacted the checkstyle, github, junit, and unix formatters at least. Not stylish or default, though.

[Copilot]

Pull request overview

Fixes truncated diagnostics (notably parser errors containing :) by removing overly aggressive message parsing in the diagnostics reporter, and adds regression coverage to prevent formatter regressions.

Changes:

• Remove colon-based message truncation from Info::new (use diagnostic.to_string() as-is).
• Add a Unix reporter unit regression test for messages containing colons.
• Add snapshot regression coverage using a parser-error fixture across multiple CLI output formatters.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

File	Description
crates/oxc_diagnostics/src/reporter.rs	Stops truncating diagnostic messages on : when building Info, preventing loss of parser error text.
apps/oxlint/src/output_formatter/unix.rs	Adds a unit regression test ensuring Unix output preserves messages containing :.
apps/oxlint/src/output_formatter/mod.rs	Adds a snapshot regression test running multiple output formatters against a parser-error fixture.
apps/oxlint/fixtures/output_formatter_diagnostic/parser-error.js	Adds a fixture that triggers a parser error containing : in the message.

[codspeed-hq]

Merging this PR will not alter performance

✅ 47 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing fix-colon-issue (09507d0) with main (024f51c)}

Footnotes

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

[connorshea]

I am not sure what is causing the failure in the tests 🤔

[camc314]

Merge activity

• Feb 21, 12:08 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Feb 21, 12:14 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Feb 21, 12:20 PM UTC: Merged by the Graphite merge queue.