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.

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

Tracking invalid type assertions #18217

andy-ms opened this issue Sep 1, 2017 · 1 comment

Tracking invalid type assertions #18217

andy-ms opened this issue Sep 1, 2017 · 1 comment


Copy link

@andy-ms andy-ms commented Sep 1, 2017

Before we had no-object-literal-type-assertion applied, there were a lot of suspicious casts.
These have all been labeled with comments containing the text GH#18217.

ajafff added a commit to ajafff/TypeScript that referenced this issue Aug 9, 2018
andy-ms added a commit that referenced this issue Aug 10, 2018

* moduleNameResolver: fix invalid assertion and avoid unnecessary work

Part of #18217

* assert nonRelativeModuleName
Copy link

@WORMSS WORMSS commented Sep 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.