This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Used checker.getTypeArguments in return-undefined rule when possible #4866
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.
PR checklist
[ ] Documentation updateOverview of change:
TypeScript no longer guarantees a .typeArguments member on the Type object, as they're apparently capable of being lazily-defined (?). Instead we're to use a
checker.getTypeArguments
method.Once 3.7 is out of beta/RC we'll be able to upgrade our dev dependency to rely on it.