-
Notifications
You must be signed in to change notification settings - Fork 152
[TASK] Make aliased class deprecation notices visible to tools #1559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+19
−7
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c834082
[TASK] Make aliased class deprecation notices visible to tools
JakeQZ 28c0b98
Add extra `class_exists()` or `interface_exists()` check
JakeQZ f45982c
Use `@phpstan-ignore-next-line` because `@phpstan-ignore` doesn't wor…
JakeQZ 2392e35
Fix typo and restrict `@phpstan-ignore`
JakeQZ File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These should be PHPStan annotations in the code with the error code and a short explanation why we do it this way. This will allow us to keep the baseline as a to-do list of thing we'd like to fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added the annotations, but they only seem to work to silence the
booleanAnd.alwaysTruewarnings (introduced by having theclass_existsandinterface_existscombined), and seem to have no effect on thebooleanNot.alwaysTruewarning.It looks like this may be a bug in PHPStan, and we may have to use
@phpstan-ignore-next-linefor the time being.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to use
@phpstan-ignore-next-line, since@phpstan-ignoreis not working. If you can figure out why, it would be nice to only exclude certain things, but I can't, and I think it's a bug in PHPStan.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I finally realized that putting
booleanNot.alwaysTruewas silencing one of the warnings, but not both of them. Having it repeated silences both warnings.