[5.5][CodeCompletion] Don't check 'InvalidAsyncContext' for imported globals #37594
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.
Cherry-pick of #37591 into
release/5.5
InvalidAsyncContext
depends on the decl context. That may case "sticky" not-recommended If it's cached for a non-async context. To workaround this, stop checkingInvalidAsyncContext
when collecting completion items for caching. Also consistently use theSourceFile
as the decl context to avoid decl context specific behavior.