About to start porting kantan.* to scala 2.13. Wish me luck.
Show this thread
-
Static code analysis, code formatting, linters, ... all the things that I like not to think about but are outside of Fury’s scope. I understand the reasoning, but it’s important to me to need one tool, not n, to be able to compile and build my projects.
I'm not sure any of those things are outside Fury's scope. But code formatting, although possible, will probably still not be recommended. It would seem to belong with the IDE instead of the build.
-
-
In case of a large team with heterogenous tooling you'd probably want to enforce a formatting check in build. At least that's what my team does with sbt-scalafmt.
-
Why integrate it with the build and not the version-control system?
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
- Show replies
-
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.