wickedOne
wickedOne
related to [this](https://github.com/squizlabs/PHP_CodeSniffer/pull/3478) issue which hasn't been tagged yet
what would be the added value of having this test on top of those defined in ``Symfony/Tests``?
to me it makes no sense to incorporate parts of another coding standard (other than the default sniffs provided by codesniffer) into this one. the whole idea is to provide...
by that sentiment it would make more sense to put out a seperate package which consists of a ``phpcs.xml`` with aggregated rules from different standards don't you think?
an added dependency which supports / replaces something which does not concern the core functionallity of a library makes sense. replacing the core functionality with the core functionality of another...
first of all sincere apologies for my ridiculous late reply on this one; a lot has been going on / happened last year or so as i guess did for...
> Declare public methods first, then protected ones and finally private ones. The exceptions to this rule are the class constructor and the setUp() and tearDown() methods of PHPUnit tests,...
i'm not entirely sure what would be the purpose of trying another coding standard within this one; are you suggesting to copy slevomat's code into this repository?
you can add the following to your php-cs-fixer config ```php 'no_superfluous_phpdoc_tags' => false, ``` symfony coding standard still states: > Add PHPDoc blocks for all classes, methods, and functions (though...
additionally you should be able to add the following snippet to your ``phpcs.xml`` ```xml 0 ```