Juliette
Juliette
Note: this would become more complex if #742 gets implemented.
The `Squiz.Commenting.FunctionComment` sniff - and other comment related sniffs in PHPCS - do not support the `array{...}` type format and never have. Reclassifying this ticket as a feature request, not...
I wonder whether it would even make sense to do this validation as early as in the `Config` class ?
Oh and another one for which the same applies: the `GitBlame` report class ;-)
For the record: #1105 will be merged without introducing new `which`/`where` logic. All the same, I believe it may still be worth introducing the suggested method. Low priority though.
The discussion in #2851 is related to this and contains some additional considerations to take into account.
I think that makes sense, but only for "closed" scope structures, like nested named functions, not for arrow functions, which are "open". As for closures and anonymous classes, I'd like...
Thanks @SergeyBiryukov! And thanks for adding the `WP_RUN_CORE_TESTS` check to the condition too.
@hellofromtonya Would you like me to rebase to get rid of the merge conflicts ?
Thanks @hellofromtonya!