Fix type check for async function with alias return type. #5429
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.
Switched to resolvedSymbol from NodeLinks instead of mergedSymbol from the type. When the return type is a type alias, we eagerly resolve the actual type. This resuls in a false positive for a type that exists as a value.
There is a minor change to the error reporting here, as I want to report the error using the name of the alias used in the return type, not the name of the resolved type of the alias. This is so you don't see an error like
"Type 'Promise' is not a valid async function return type"
when you use an alias for Promise. This has the side effect of not including the type arguments in the error message, but I think that's acceptable.Fixes #5333.