Skip to content
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

Merged
merged 5 commits into from
Oct 5, 2019
Merged

Used checker.getTypeArguments in return-undefined rule when possible #4866

merged 5 commits into from
Oct 5, 2019

Conversation

JoshuaKGoldberg
Copy link
Contributor

PR checklist

Overview 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.

Josh Goldberg added 5 commits October 2, 2019 16:32
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.
@adidahiya adidahiya merged commit f0236ee into palantir:master Oct 5, 2019
@JoshuaKGoldberg JoshuaKGoldberg deleted the checker-type-arguments branch October 5, 2019 18:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI testNext failures with typescript@3.7.0-dev.20190928
2 participants