Julien Falque
Julien Falque
There are no rules for doing that at the moment.
No I think this is quite new :)
Closing in favor of #6395. Thank you anyway @drupol for the time you put on this.
This is an issue in `class_attributes_separation`. This can be reproduced with this snippet: ```php
I think we cannot reliably assume a comment is "tied" to the next element unless it's a DocBlock. Always ignoring regular comments seems like a more sensible choice to me....
```php 'no_whitespace_before_comma_in_array' => true, ``` removes any whitespace whereas ```php 'multiline_whitespace_before_statement_end' => ['comma_strategy' => 'no_new_line'], ``` removes any whitespace that contains a newline.
Indeed. Note this is also true with the fixer being deprecated here: ```php 'no_whitespace_before_comma_in_array' => true, ``` and ```php 'multiline_whitespace_before_semicolons' => [ 'strategy' => 'no_multi_line', ], ``` have the same...
Expect tests to fail for now. So... * `no_whitespace`: always removes spaces; * `no_new_line`: pretty much the same but only if a newline is found; * `new_line_for_chained_calls`: adds a new...
No need to ping me, I didn't forget about my WIP branches. I just don't have the time to finish those right now but I'll do it eventually :)