Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Roadmap for v1.0 #730
Scalafmt v0.1 came out in March 2016. Here are some stats in January 2017
It's been a really great year, and I'm super thankful for everyone who has been involved in the project so far. I have enjoyed it a LOT and I look forward to continue working on scalafmt.
The formatting output is fairly stable now (big changes like in v0.5.0 to the default style typically provide fallback config for old styles). I think now is a good time to start thinking about releasing v1.0.
I saw somewhere on the interwebs.
I admit it's a bit cheezy, but it does strike a chord with me.
These are organizational things I'd like to get done first
referenced this issue
Feb 13, 2017
Something that has been bugging me, and maybe 1.0 is the place to do this: do we want Scalafmt to be a fine-grain or an opinionated, holistic auto-formatting tool?
Currently we are supporting both of these approaches which can cause even more confusion. I'm on the camp of "full, holistic" reformat where we don't give the option for stuff like how many indents to make on a given closure. Of course we can still support different holistic styles for different sections (
That is a great point @pjrt. My view is that scalafmt should be opinionated and provide a unified formatting look across source files. Most users should only have to configure
Is there anything in particular that you would like to change to make scalafmt more opinionated/holistic? For example, we could removesome sections from the online configuration docs https://olafurpg.github.io/scalafmt/#Configuration
I would argue that scalafmt is already quite opinionated. The only places where the users controls lines breaks is
List( 1, 2 )
even though it could fit within the max column setting.