Anthony Clark

As @bakerkretzmar mentioned in pr #288 we may want to also drop support for PHP 7.4 and support 8.0+

The linting of group use with traits is handled in [PRS-12](https://www.php-fig.org/psr/psr-12/) section 4.2: > Each individual trait that is imported into a class MUST be included one-per-line and each inclusion...

I agree with @bakerkretzmar here, thanks for the suggestion @Wulfheart. This can always be added to a custom preset for your own use 👍

Thank you @bakerkretzmar 🙌

For me to reference later: - Related to blank line https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/6365 - Add to standards

@sbine this looks good! I'm inclined to add this to [Tighten Coding Standard](https://github.com/tighten/tighten-coding-standard/pull/9) using [php_unit_test_annotation](https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/master/doc/rules/php_unit/php_unit_test_annotation.rst). This will give us both linting and fixing without us having to maintain this functionality....

Thanks, @bakerkretzmar for updating this!

@ifox, I agree with your hesitation. Seems like without publishing some starting point to the front end, neither option is ideal. The documentation I've seen on the Twill site around...

The spacing is from TLint's `OneLineBetweenClassVisibilityChanges` > Class members of differing visibility must be separated by a blank line

Right now, `OneLineBetweenClassVisibilityChanges` doesn't distinguish between const/properties, it only looks at visibility changes. I think we would need an additional linter/formatter for class attribute groups, something like `OneLineBetweenClassAttributeGroups`. Pint's Laravel...