0.3.27

Type	Description	Link
Improvement	Case statements with a body consisting of a single block now inline their block.	#252

0.3.26

Type	Description	Link
Fix	Make lambda/assignment logic more resilient so it doesn't crash when encountering long comments.	#203

0.3.25

Type	Description	Link
Fix	Fix bug in 0.3.24 that could sometimes cause a NPE when encountering a newline right after a string concatenation expression.	#193

0.3.24

Type	Description	Link
Improvement	Long annotation args are now partially inlined, such that concatenated strings look better.	#191
Improvement	Preserve the user's newlines in a long string concatenation (defined as a concatenation with + where at least one expression is a literal string).	#192

0.3.23

Type	Description	Link
Improvement	Reduce situations where an inlined lambda can get a newline after the arrow, and allow inlining new Class() calls in more contexts.	#169

0.3.22

Type	Description	Link
Fix	Method references are no longer split onto their own line unless the expression they're referencing is also completely split.	#164

0.3.21

Type	Description	Link
Fix	Support source=9 across all formatter steps.	#163

0.3.20

Type	Description	Link
Fix	Only allow expressions with prefix to be inlined after a lambda/simple expression if they contain method calls.	#161

0.3.19

Type	Description	Link
Improvement	More strictly control when we can inline a chunk of code followed by an expression lambda, to avoid pathological cases with a very simple expression being split onto the next line.	#147

0.3.18

Type	Description	Link
Fix	Only service load the formatter implementation once, rather than once per gradle project. This avoids gradle potentially exceedding the MaxMetaspaceSize and throwing java.lang.OutOfMemoryError: Metaspace.	#158