Juliette
Juliette
@ehausen Yes, fatal errors break things. Not sure what your usecase is, but you could just use the underlying tooling directly: https://github.com/PHPCompatibility/PHPCompatibility
Yes, that standard was my first thought, unfortunately I know from experience that that standard is not being actively maintained, so chances of the sniff ever getting merged are slim...
> The Generic DeprecatedFunctionsSniff is basically a wrapper over the Generic ForbiddenFunctionsSniff, with only some details making them different. > While the Forbidden Sniff supports showing the defined alternative, curiously...
Related to #2222 which will make creating this sniff so much easier ;-)
@TomasVotruba I expect it to be ready for PHPCS 3.5.0 which includes lots of other goodies which will be useful for this too. See #2189
@Danack @mallardduck I appreciate your thoughts, but my experience is different. Things which have been deprecated previously, will be removed in most cases on the next major - i.e. PHP...
> Of course, solving this in a way that does not require allowing dynamic properties for everything is always preferred, if not too hard to realize :) @nikic Please see...
@andypost Not sure what you mean ? https://3v4l.org/sg5R0
I have opened PR #3629 to address this. The PR implements option 6 with some caveats. Please see the extensive write-up in the PR description for full details.
> or to call the `setSniffProperty()` method on the `Ruleset` object directly (which may happen in custom test frameworks for external standards). I could possibly make this BC-break smaller if...