Sorry I didn't follow up in #466
I'm not sure about the stability of v2 yet. Some projects (SciML) seem to already moved to it. Yet the tooling doesn't seem to fully support it. I often use vscode which is stuck with v1, julia-vscode/julia-vscode#3819, and then I end up constantly reformatting code between v2-v1-v2 which sometimes breaks something on the way

Thanks for looking into this! I have not thought about it much but I am still in favor of figuring out a way that still sticks to using Formatter v2.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.16%. Comparing base (531260f) to head (3661208).
⚠️ Report is 4 commits behind head on master.

@@           Coverage Diff           @@
##           master     #472   +/-   ##
=======================================
  Coverage   97.16%   97.16%           
=======================================
  Files         121      121           
  Lines        7020     7020           
=======================================
  Hits         6821     6821           
  Misses        199      199           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This should be ready for review now. Please do not squash if you merge, so that we can have the single re-formatting commit hidden from git-blame in the future.

Thanks for the fix! I do not know how I missed something with so many loud warnings. That is now cherrypicked and the precommit config file is also removed.

I will wait for tests to pass without warnings and will merge. After that I will setup a git blame exclusion file so that the formatting commit does not pollute git blame.

Would you mind creating a new release including this PR, such that the warnings are fixed?

Thanks for the reminder, I will do so in a couple of minutes.

Great, thanks a lot!