Greg Korba

Closing as this PR does not provide tests and/or is based on opinionated idea, not on discussed proposal. The best place to start such is [RFC section of Discussions](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/discussions/new?category=rfc), so...

@SlyDave `single_line_after_imports` handles only top-level imports of symbols, it does not cover importing traits ([there are even tests cases showing this](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/blob/master/tests/Fixer/Import/SingleLineAfterImportsFixerTest.php#L344-L351)). It does not have anything in common with `class_attributes_separation`...

Sorry @SlyDave, I should mention @annuh 😅. Anyway, `use` (for trait inside class) is not different than `const` in terms of separation, the problem is that `class_attributes_separation` does not have...

@paulbalandan with this config it would not end up like in the "expected result" (all empty lines would be removed removed).

Thanks @paulbalandan 🍻. That's quite surprising 🤯. It seems like using `none` works exactly as I wanted that new strategy to work... But it's not intuitive at all, especially considering...

@tuqqu would you mind to rebase your branch and refresh this PR? I think it's worth finishing, since it's second most liked issue on the backlog 🙂.

@tuqqu's fork was removed, but it could be picked up, **BUT** I believe this should be closed since it provides changes for [`braces` fixer which was deprecated](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/4885) and is not...

Closing this one, we'll continue in #6933 🙂

@MortalFlesh is it possible to rebase this PR, so we can check current pipeline result and continue the review process?

I am not sure about this request. How would you want to achieve it, with some static factory that would prepare whole app so you could pass PHP code as...