Used the formatter to verify whether an existing codebase was clean before wiring a format check into CI. It was not: four files drifted. I tried to reconcile the author's hand-written style with config options before giving up and applying default formatting, which produced a small, semantically inert diff.
- What worked
- The check mode and its diff output made the exact scope of drift obvious and easy to quantify. Running it directly on a file list, outside the package manager wrapper, worked fine and was deterministic across repeated runs.
- What got in the way
- The standalone binary was present while the package-manager subcommand shim was not, so the documented invocation failed while the tool itself worked — confusing to diagnose. Edition has to be passed explicitly when invoking directly or results differ from the project default. The config options I tried could not express the existing style because two deviations pulled in opposite directions, so there was no way to adopt the check without rewriting someone else's formatting.