- Issue created by @spokje
- Status changed to Needs review
11 months ago 1:41pm 3 January 2024 - Status changed to Needs work
10 months ago 5:51pm 27 January 2024 - 🇦🇹Austria klausi 🇦🇹 Vienna
Thanks, just one minor comments from me.
Could this disrupt custom Drupal projects where developers use trigger_error() for deprecations in their own project? Maybe this is not common. Developers can also disable individual rules, so there are workarounds in such a case.
In my projects we don't use trigger_error() and mostly rely on custom PHPStan rules that flag deprecated function invocations.
- Status changed to Needs review
10 months ago 2:05pm 29 January 2024 - 🇳🇱Netherlands spokje
Thanks for the review @Klausi!
Added fixer and addressed your comments.
Could this disrupt custom Drupal projects where developers use trigger_error() for deprecations in their own project?
If and when core turns this rule on it would.
Maybe this is not common.
Found 5 occurrences with http://codcontrib.hank.vps-private.net/search?text=E_USER_DEPRECATED&fil...
One of them (bat) even has a convenient// phpcs:ignore
straight above it.So I would say not very common indeed, and as you said disable-able if no @ there on purpose.
- 40d9024d committed on 8.3.x
feat(UnsilencedDeprecation): Add sniff for unsilenced trigger_error()...
- 40d9024d committed on 8.3.x
- Status changed to Fixed
9 months ago 12:58pm 16 February 2024 - 🇦🇹Austria klausi 🇦🇹 Vienna
Ok, then let's do this! Thanks a lot for your patience and rerolling.
Automatically closed - issue fixed for 2 weeks with no activity.