Spotless Rule

[Taskeren]

The current spotless rule will insert a return (\n) before the 3rd function call in a chained function call, like:

"Hello!".toString().toString().toString();

will be transformed to

"Hello!".toString()
    .toString()
    .toString()

This is very ugly in almost all situations.

This is nothing about the line length limit, as I've tested it.

[RenanOSX]

You can disable spotless if you don't like it on "gradle.properties" by uncommenting "disableSpotless = true"

[glektarssza]

@Taskeren What are you proposing as an alternative? What is the request here? I get you don't like the current behaviour, that's understandable (and I'm not a fan of it either) but then please propose an alternative. Simply saying "I don't like this" is not productive.

[Taskeren]

@Taskeren What are you proposing as an alternative? What is the request here? I get you don't like the current behaviour, that's understandable (and I'm not a fan of it either) but then please propose an alternative. Simply saying "I don't like this" is not productive.

I was just showing the problem here. But as you asked, I'd prefer one call per line with first call in the first like:

"FOO".doSomethingElse0()
    .doSomethingElse1()
    .doSomethingElse2()
    .doSomethingElse3();

And it should have such option to only make it multiple line when one line can't them all (exceeds the line limit).

And the problem is that it will always make it multiple line.

[Taskeren]

And I think it can be documented that how to customize our own rules (both spotless and style check or something) in a very simple explicit way.

[RuiXuqi]

I would be happy if the spotless configuration could be configured instead of being hard-coded and unmodifiable in com.gtnewhorizons.gtnhconvention.