I do a lot of work in go and I really enjoy having gofmt around. Formatting code in a consistent way is one less thing that I need to think about, and when working in larger groups, one less thing to constantly debate. I do think that scalafmt is a bit more opinionated in certain ways, but I think coming up with a more agreeable configuration is better than not having it at all.
// Mike -----Original Message----- From: Mike Beckerle <[email protected]> Sent: Friday, June 23, 2023 12:13 To: [email protected] Subject: I am really hating scalafmt We added scalafmt, and I have not done much coding since that time. Now that I have, I hate it. It turns this: val optURI = Misc.getResourceRelativeOption(sysId, baseURI) orElse Misc.getResourceRelativeOption(removeInitialUpwardPathSteps(sysId), baseURI) into: val optURI = Misc .getResourceRelativeOption(sysId, baseURI) .orElse( Misc.getResourceRelativeOption(removeInitialUpwardPathSteps(sysId), baseURI) ) This is awful. And you can't override it, because if your code doesn't conform, it fails a format check. I suggest we just turn off this scalafmt stuff.
