About to start porting kantan.* to scala 2.13. Wish me luck.
Show this thread
-
He mentioned that in response to my question and it's a good use case so I will re-ask: how would you propose to set up static code analysis, test coverage, formatting, linting, wart finders and such with fury?
I don't believe code formatting should be part of the build... but someone could write a "compiler" which compiles source code to source code. It just doesn't seem sensible to reformat all your code every time you change anything... before committing, though, sure.
-
-
Almost all the other things you list are just compiler plugins, so you would just depend on them. But static analysis is more interesting. I'm looking at finding sufficiently general solutions to that, or failing that, integrating some of the use cases directly into Fury.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Metals using lsp to perform scalafmt is the answer for code formatting imo. I agree: no need to be part of the build
-
Disagreed. I want to fail builds whose style is not valid, so scalafmt needs to be somewhat part of the build, to fail in CI
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.