Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assignability checks in API #13502

Closed
andy-hanson opened this issue Jan 15, 2017 · 5 comments
Closed

Assignability checks in API #13502

andy-hanson opened this issue Jan 15, 2017 · 5 comments
Labels
Duplicate An existing issue was already created

Comments

@andy-hanson
Copy link

andy-hanson commented Jan 15, 2017 •
edited

Could isTypeAssignableTo be exposed on the type-checker for use by API consumers? This would be helpful for analyzing code using type information. I would like to check instanceof expressions for assignability in a lint rule (palantir/tslint#2046).
getBaseConstraintOfType would also be useful for doing checks inside generic functions.
isTypeAssignableTo would also be useful for a no-unnecessary-cast rule.
@andy-hanson
Copy link
Author

On that note, it would be useful to have some way of accessing control flow information too. palantir/tslint#2038 (comment)

@danvk
Copy link
Contributor

danvk commented Jan 22, 2017

Related to #11728

I'd also like have this exposed for danvk/typings-checker#15

@andy-hanson
Copy link
Author

Would be resolved by #9943.

@ghost ghost mentioned this issue Mar 24, 2017
Closed
This was referenced Apr 2, 2017
Closed
Closed
Merged
@andy-hanson andy-hanson mentioned this issue May 4, 2017
Closed
@RyanCavanaugh RyanCavanaugh added the Needs Investigation This issue needs a team member to investigate its status. label May 24, 2017
@mhegazy
Copy link
Contributor

mhegazy commented Nov 1, 2017

Duplicate of #9879

@mhegazy mhegazy marked this as a duplicate of #9879 Nov 1, 2017
@mhegazy mhegazy added Duplicate An existing issue was already created and removed Needs Investigation This issue needs a team member to investigate its status. labels Nov 1, 2017
@typescript-bot
Copy link
Collaborator

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Duplicate An existing issue was already created
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@danvk @andy-hanson @RyanCavanaugh @mhegazy @typescript-bot