Skip to content

Commit

Permalink
0.2.4 release
Browse files Browse the repository at this point in the history
  • Loading branch information
godenji committed Oct 25, 2017
1 parent 089f694 commit c4f3fc9
Show file tree
Hide file tree
Showing 3 changed files with 24 additions and 3 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
0.2.4 (25/October/17)

* Updated to Scala 2.12.4
* Updated to Sbt 1.0.2
* Added support for multiline param groups (fixes #77)

0.2.3 (10/August/17)

* Updated to Scala 2.12.3
Expand Down
19 changes: 17 additions & 2 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Usage within a project

Have a use for the scalariform source code directly? You can use it as a build dependency: ::

"org.scalariform" %% "scalariform" % "0.2.3"
"org.scalariform" %% "scalariform" % "0.2.4"

Integration with Eclipse
------------------------
Expand Down Expand Up @@ -297,7 +297,7 @@ alignSingleLineCaseStatements.maxArrowIndent

Default: ``40``

When ``alignSingleLineCaseStatements`` is ``true``, this is a limit on
When ``alignSingleLineCaseStatements`` is ``true`` there is a limit on
the number of spaces that can be inserted before an arrow to align it
with other case statements. This can be used to avoid very large gaps,
e.g.:
Expand All @@ -309,6 +309,21 @@ e.g.:
case ccc => 2
}
allowParamGroupsOnNewlines
~~~~~~~~~~~~~~~~~~~~~~~~~~

Default: ``false``

When ``allowParamGroupsOnNewlines`` is ``true`` the default behavior of collapsing
param groups into a single line is disabled. This allows for the following formatting style:

.. code:: scala
def foo[T]
(a: A)
(b: B)
(implicit t: T)
compactControlReadability
~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
2 changes: 1 addition & 1 deletion version.sbt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
version in ThisBuild := "0.2.4-SNAPSHOT"
version in ThisBuild := "0.2.4"

0 comments on commit c4f3fc9

Please sign in to comment.