Skip to content

Drop phpstan-deprecation-rules - #411

Draft
shanerbaner82 wants to merge 1 commit into
mainfrom
chore/drop-phpstan-deprecation-rules
Draft

Drop phpstan-deprecation-rules#411
shanerbaner82 wants to merge 1 commit into
mainfrom
chore/drop-phpstan-deprecation-rules

Conversation

@shanerbaner82

Copy link
Copy Markdown
Contributor

This package flags every call to anything marked @deprecated, which means tagging an internal helper fails the build on the call sites that are supposed to exist. It came up on #410: a back-compat shim carried a @deprecated note aimed at whoever deletes it later, and PHPStan reported all five uses from the two compilers that legitimately construct it. The choice was a red build or dropping the note, and neither is right for code with no consumers outside core.

Nothing else depends on it. The analysis runs at level 0 and these rules arrived through phpstan/extension-installer rather than anything in phpstan.neon, so removing the requirement is the whole change.

The package reports every call to anything marked @deprecated, which fails the
build for internal code that is tagged for a future reader rather than for
consumers — a back-compat shim's own call sites are the case that prompted
this. Deprecating an internal helper should not mean choosing between a red
build and dropping the note.

Nothing else here relies on it: the analysis runs at level 0, and these rules
came in through phpstan/extension-installer rather than phpstan.neon.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015NQcYw62aFuTwy8RrZT6wJ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant