Update java supertype processing #3997
Open
+103
−26
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.
The processing of supertypes for java source would convert
PsiClassType
s toPsiClass
es while creatingAncestryNode
s. This meant that the type parameters used for the supertypes were from thePsiClass
definition instead of thePsiClassType
usage like they should be.For example, in the following java code:
The super class type of
Foo
should beBar<String>
. When processing the supertypes ofFoo
, thePsiClassType
representingBar<String>
was converted to aPsiClass
. ThePsiClass
reflects the definition ofBar
, soBar<T>
became the super class type instead ofBar<String>
.Fixes: #3996