If I understand right right now running check script ruleset, it check any usage of deprecated call inside script based on the @deprecated annotations defined by the ruleset (usually vendor or composer.lock).
However you might want to use this tool four handling migration in your own app, ex:
/**
* @deprecated Use NewModel instead
*/
class LegacyModel {...}
class NewModel {...}
This is doable by running deprecation-detector src src for example, but I find it weird. Plus that means in this use case, you actually have to run two times the command:
If I understand right right now running
check script ruleset
, it check any usage of deprecated call inside script based on the@deprecated
annotations defined by the ruleset (usuallyvendor
orcomposer.lock
).However you might want to use this tool four handling migration in your own app, ex:
This is doable by running
deprecation-detector src src
for example, but I find it weird. Plus that means in this use case, you actually have to run two times the command:It would make more sense IMO to include
src
(or rather the directory being checked) to the ruleset by default.