Skip to content

Conversation

@yrodiere
Copy link
Member

To be reviewed commit by commit: the first two commits introduce massive changes in the settings file format (IntelliJ's fault, not mine) but no actual style changes.

This does not change anything to the style, this is the same style but
as written with a newer version of IntelliJ.
The purpose of this commit is to make the diff of the next commits
understandable.
This does not change anything to the style, this is the same style but
as written with a newer version of IntelliJ.
The purpose of this commit is to make the diff with the OGM style
understandable.
Since we are also using it in Search.
…ters in NoORM projects

I.e. do this:

foo.someMethod().someOtherMethod().yetAnotherMethod( firstParam,
        secondParam, thirdParam );

Or this:

foo.someMethod().someOtherMethod().yetAnotherMethod(
        firstParam, secondParam, thirdParam
);

But certainly not this:

foo.someMethod().someOtherMethod().yetAnotherMethod( firstParam,
                                                     secondParam,
                                                     thirdParam );

Nor this:

foo.someMethod().someOtherMethod().yetAnotherMethod(
                                                     firstParam,
                                                     secondParam,
                                                     thirdParam
                                                   );

The main reason being to avoid wasting space, but also to avoid IntelliJ
inserting spaces after tabs in the indent to be exactly aligned.
This is a rule that we enforce with checkstyle, so there's no way around
it. We may as well take it into account in the IntelliJ styles.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant