Check if at least one resolution for module attribute references is valid #1781
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.
Fixes #1767
Changelog
Enhancements
annotator.ModuleAttribute
to KotlinBug FIxes
Check if at least one resolution for module attribute references is valid
Previously, it was checked if module attributes resolved to exactly one declaration, but this is no longer true with the looser reference resolution that allows invalid results for PisPolyVariantReference.
resolve()
will returnnull
when there is more than one result frommultiResolve
even if some are invalid, so we need to explicitly check if thePsiReference
is aPsiPolyVariantReference
and if so check if any are valid.Fix deprecation warnings for
annotator.ModuleAttribute
.Quick fixes for inlinables in
annotator.ModuleAttribute
.