autoimports checks for merged parent if symbol parent is not found #59582
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 adds a check to
importFixes/autoimports that finds the parent ifsymbol.parentdoes not exist.When merging symbols that are exported through export lists and then augmented in module augmentations (for example, interfaces), the merged symbol does not have a parent. The augmentations work correctly with the merged symbols not having parents. Since the parent is not needed for typechecking and seems to only be needed in this case of autoimports, we will save memory by continuing to not set
.parent. (we can revisit this if we see.parentis needed elsewhere in the future).Fixes #58907
Closes #58965 (more info in comment)
(the aliased case mentioned here still crashes but because of a different autoimports bug, so opened up a new issue: #59583)