Java: Fix CSV subtype interpretation #6215
Merged
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.
This fixes a bug in the interpretation of the subtypes/overrides csv column. Jumping to subtypes and matching members on the subtype doesn't make sense since generics mean that the signature might be different. As an example,
MultivaluedMap.puthas an (erased) signature that's different from the overriddenMap.putdue toVbeing instantiated toList<V>. The first two commits highlights this problem.The fix is to match the member on the supertype and jump to overrides of that member instead of matching the overriding member on the subtype.