+1 to backport it now; the release is already being finalized after all.
On 04/05/2022 10:13, Timo Walther wrote:
Hi everyone,
The 1.15 release is almost out. We should still discuss whether we
want to backport scalafmt to the release-1.15 branch. Currently, it is
quite cumbersome to backport fixes in the table planner.
It seems scalafmt has stabilized in master. Are you ok with
backporting the changes now and apply the reformatting? The only
downside could be that exception/error messages might use a slightly
different line number for Scala code.
Any other downsides that I forgot? Or other opinions on this topic?
Thanks,
Timo
