Single property optimizations

[amis92]

The styling is a matter of preference. I'd like to keep this project coherent, formatting-wise as well. Which means, please keep the style uniform, same as in other source files.

That said, I don't find a lot of line breaks helping - on the contrary, it divides lines into blocks, silently hinting about some separation. And separation means to me - maybe that's another method? So if you feel a need to separate things, refactor the block to a new method. (An exception to this rule is in unit tests, where line breaks naturally separate the three As of Arrange-Act-Assert).

Style wise, in terms of formatting complicated invocation trees:

• a multiline expression starts on new line (so not in the same line as variable declaration or a return)
• every invocation has its own line
• arguments are in separate lines, 1 more indent than invocation
• fluent/dot transformations (invocations on other expressions' results) are in new line, indented the same as the target

That's how this project formats source code.

[megakid]

Understood - feel free to edit this PR to your own style. If the style was explicitly written somewhere or enforced via .editorconfig you may have a better chance of keeping the formatting clean without the frustrating back-and-forth over small formatting issues.

[megakid]

Wrong button

[amis92]

feel free to edit this PR to your own style

This is probably for the best then.

.editorconfig is on todo, however it wouldn't help much for those issues.

[amis92]

Thanks!