Juliette
Juliette
Loosely related to #120
@kczx3 Thanks for adding the link. And yes, increasing awareness about these changes is exactly what this issue is about ;-)
Related #58: proposed removal of the `Zend.Debug.CodeAnalyzer` sniff in 4.0. If this PR proceeds, the sniff should be included in the sniffs to get a deprecation notice in the last...
@mbomb007 This ticket is not directly related to exit codes. It is about how to handle (some of the) "Internal" errors.. The current handling has a side-effect on the exit...
@greg0ire Correct and yes, I don't intend to let things wait for too long. I also have a GH Actions workflow already set up which automatically labels PRs with [merge...
@greg0ire Just read up on octopus merges, hadn't come across that term before. And no, when I do those kind of "merge sprees", I will merge one PR at a...
> I would like more version that `Sniff` interface will be preserved and it would be possible to add `FixableSniff` interface to mark the sniff as fixable. > > However...
@stronk7 Thanks for your input. > Take for example `AbstractScopeSniff`, there are dozens of Sniffs extending it... I imagine that some are "fixable" and some are not... and it doesn't...
> Last question… and which interface will abstract sniffs implement? In most cases, in my thinking, that would be `FixableSniff`, which would effectively mean that the child classes are _allowed...
I'm not sure I fully understand your problem. You can already use option 2 by having an explicit `` at the start of the subdirectory ruleset. Making that implied will...