🐛 --apply-unsafe and --apply CLI arguments cause errors not to be returned

[EvHaus]

Environment information

CLI:
  Version:                      12.1.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.2.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.6.2"

Rome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Discovering running Rome servers...

Incompatible Rome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ℹ Rage discovered this running server using an incompatible version of Rome.

Server:
  Version:                      12.1.0

What happened?

As discussed on Discord, I noticed that when I run rome check --apply-unsafe . and there are errors, the output says:

Fixes applied to the file, but there a still diagnostics to address.

But if I run rome check . then it shows me the actual errors.

It would be great if there was a way for the CLI to show both of those behaviours together, ie. I want the fixes to be applied but also errors for what couldn't be fixed shown too.

This is how ESLint works.

Expected result

CLI output would show remaining errors that couldn't be auto-fixed.

Code of Conduct

• I agree to follow Rome's Code of Conduct