Scalastyle VS Scalafix

Compare Scalastyle vs Scalafix and see what are their differences.

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
Scalastyle Scalafix
1 5
679 687
0.0% 0.4%
0.0 9.0
over 2 years ago 5 days ago
Scala Scala
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Scalastyle

Posts with mentions or reviews of Scalastyle. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-08.
  • Checklist for learning Scala
    5 projects | dev.to | 8 Feb 2021
    Find a code conventions document: the online Scala course that I’ve started uses Scalastyle for enforcing the style of the code. If it’s good enough for the Scala core team, it’s good enough for me.

Scalafix

Posts with mentions or reviews of Scalafix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-12.
  • Which static analysis tool do you use for Scala?
    8 projects | reddit.com/r/scala | 12 Jan 2022
    Scalafix
  • Dragging Haskell Kicking and Screaming into the Century of the Fruitbat :: Reasonably Polymorphic
    3 projects | reddit.com/r/haskell | 13 Nov 2021
    scala-fix seems relevant for the /= removal problem.
  • Newspeak and Domain Modeling
    4 projects | news.ycombinator.com | 29 Jun 2021
    or `NonUnitStatements` without explicit annotation.

    This effectively locks you into writing pure code (you can extend the linter to cover other things like not using `Future` or not using Java libs outside of `MonadError` from cats[4]). The linters operate on typed ASTs at compile time, and have plugins for the most popular scala build tools. Coupled with `-XFatalWarnings', you can guarantee that nothing unexpected happens unless you explicitly pop the escape hatch, for the most part.

    You can still bring in external libraries that haven't been compiled with these safties in place, so you aren't completely safe, but if you use ZIO[5]/Typelevel[6] libraries you can be reasonably assured of referentially transparent code in practice.

    There are three schools of thought, roughly, in the scala community towards the depth of using the type system and linters to provide guarantees and capabilities, currently:

    1) Don't attempt to do this, it makes the barrier to entry to high for Scala juniors. I don't understand this argument - you want to allow runtime footguns you could easily prevent at compile time because the verifiable techniques take time to learn? Why did you even choose to use a typesafe language and pay the compilation time penalty that comes with it?

    2) Abstract everything to the smallest possible dependency interface, including effects (code to an effect runtime, F[_] that implements the methods your code needs to run - if you handle errors, F implements MonadError, if you output do concurrent things, F implements Concurrent, etc.) and you extend the effect with your own services using tagless final or free.

    3) You still use effect wrappers, but you bind the whole project always to use a concrete effect type, avoiding event abstraction, thus making it easier to code, and limiting footguns to a very particular subset (mainly threadpool providers and unsafeRun or equivalent being called eagerly in the internals of applications).

    My opinion is that smallest interface with effect guarantees (#2) is best for very large, long maintenance window apps where thechoice of effect runtime might change(app), or is out of the devs' control (lib); and #3 is best for small apps.

    TL/DR; You can go a really, really long way to guaranteeing effects don't run in user code in scala. Not all the way like Haskell, but far enough that it's painful to code without conforming to referential transparency.

    1. https://github.com/scalacenter/scalafix

    2. https://github.com/scalaz/scalazzi

    3. http://www.wartremover.org/

    4. https://typelevel.org/cats/api/cats/MonadError.html

    5. https://zio.dev/

    6. https://typelevel.org/

  • Scala noob question. Parameter of type Option. Why does scala compiler allows passing null as an argument?
    1 project | reddit.com/r/scala | 10 May 2021
    I actually still recommend using WartRemover, at least until there's an equivalent ScalaFix ruleset that's as effective.
  • Teaching exercises with custom error messages
    1 project | reddit.com/r/scala | 2 Mar 2021
    Probably linting rules defined in Scalafix. See https://github.com/scalacenter/scalafix/blob/master/scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala#L11 for an example.

What are some alternatives?

When comparing Scalastyle and Scalafix you can also consider the following projects:

scalafmt - This repo is now a fork of --->

Scapegoat - Scala compiler plugin for static code analysis

Wartremover - Flexible Scala code linting tool

Scalariform - Scala source code formatter

Scoverage - Scoverage Scala Code Coverage Core Libs

Linter - Static Analysis Compiler Plugin for Scala

Metals - Scala language server with rich IDE features 🚀

Mill - Your shiny new Java/Scala build tool!