-
Notifications
You must be signed in to change notification settings - Fork 571
Generics on phpstan-type aliases #5378
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
Draft
shmax
wants to merge
28
commits into
phpstan:2.1.x
Choose a base branch
from
shmax:generics-on-phpstan-types
base: 2.1.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 1 commit
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
b973b5f
first pass
shmax eb67c21
enforce required generic params
shmax 6fdb88f
more tests
shmax b27d26e
tests for invalud usage
shmax 4f18071
fix regression
shmax 95abc98
add more scenarios to test fixture
shmax f529784
remove empty patch
shmax 590daa6
coalesce to empty array
shmax b8e0c55
lint
shmax a94b14b
fix use function ordering
shmax beedafb
fix generic alias resolution: skip alias path when name resolves to a…
shmax e023f92
remove resolveWithDefaults: bare generic alias usage restores old Tem…
shmax 04c8aec
fix phpstan self-analysis errors: ignore property.notFound, add null …
shmax 0195d7d
remove ignore
shmax 95ae9e4
add property.notFound baseline entry for PHP < 8.0 (phpdoc-parser lac…
shmax 2fd32f3
move property.notFound baseline entry to universal phpstan-baseline.n…
shmax 89423b3
fix generic alias bare-usage resolution and data-provider parameter s…
shmax 6c7322d
update baseline after rebase onto 2.1.x
shmax 2321f59
add temp patches
shmax 5726a40
use LateResolvableType
shmax 6426482
remove
shmax fb9203b
lint
shmax d7fe98c
fix array vs list error
shmax e3aebe9
remove dead code
shmax ef31211
fold getRawGenericTypeAliasesUsage into getNonGenericObjectTypesWithG…
shmax 106b589
update lock hash
shmax 45ba91b
lint
shmax 57a2395
remove unnecessary BC coverage from generic type alias resolution
shmax 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
fix generic alias resolution: skip alias path when name resolves to a…
… known class
- Loading branch information
commit beedafbf1f2faf6c74f266bdea7c0d1fb0efbea7
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
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.
I don't think we need this BC coverage. It's true that
MyList<string>would be resolved to an actual class even ifMyListtype alias existed, but who the hell would do that...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.
Sure. Removed, thank you.