Difference between lint and fix

[yogeshgalav]

Expected Output: duster command should fix fixable errors and show remaining errors in detail.
current output:
Lint command show errors in proper detail but does not fix fixable errors.
Fix command fixes errors but doesn't show what errors are remaining, it only show count of errors remaining.

Should I run both in husky pre-commit hook?

[onairmarc]

Lint is used to highlight errors. Fix is to apply the style configuration. You do not need to run Lint before running Fix.

[Joel-Jensen]

Agree on this issue, many times where I get "3 unfixable error" and I'm like "thanks, but where?". Then after deepdiving into PHP_CodeSniffer command flags and the source code here I finally realise the same thing I have done all the other times and forgot - just runt lint and it will display the errors more verbose.

Not sure about the correct way forward for this if the verbose output is not desired on fix, and maybe a skill issue, but there's room for DX-improvement. Maybe just hint about running lint instead if it fails or run it automatically?