Skip to content

Issues: microsoft/TypeScript

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

jsDoc intellisense support for @augments/@extends Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Domain: JavaScript The issue relates to JavaScript specifically Domain: JSDoc Relates to JSDoc parsing and type generation Suggestion An idea for TypeScript
#30943 opened Apr 15, 2019 by aliemre1990
[RFC] Improved UX via --noExplicitErrors Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Domain: Error Messages The issue relates to error messaging In Discussion Not yet reached consensus Suggestion An idea for TypeScript
#30689 opened Apr 1, 2019 by DanielRosenwasser
Undocumented node_modules/@types fallback strategy for classic module resolution Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript
#29443 opened Jan 16, 2019 by andy1547
Compiler option for implicitly adding this context on class member methods Add a Flag Any problem can be solved by flags, except for the problem of having too many flags In Discussion Not yet reached consensus Suggestion An idea for TypeScript
#28548 opened Nov 15, 2018 by flash1293
5 tasks done
Allow minimal type checking of JavaScript files Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Domain: JavaScript The issue relates to JavaScript specifically In Discussion Not yet reached consensus Suggestion An idea for TypeScript
#28448 opened Nov 9, 2018 by nwshane
replace implicit 'any' with 'unknown' Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript
#27265 opened Sep 21, 2018 by mmkal
4 tasks done
Add an option to force source maps to use absolute paths? Add a Flag Any problem can be solved by flags, except for the problem of having too many flags In Discussion Not yet reached consensus Suggestion An idea for TypeScript
#26531 opened Aug 18, 2018 by saschanaz
Allow type annotation on catch clause variable Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript
#20024 opened Nov 15, 2017 by jaredru
[Suggestion] Compiler Flag to treat types as immutable Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Needs Proposal This issue needs a plan that clarifies the finer details of how it could be implemented. Suggestion An idea for TypeScript
#16317 opened Jun 7, 2017 by battmanz
Flag for strict default function this types for call-site and assignability checking (--strictThis) Add a Flag Any problem can be solved by flags, except for the problem of having too many flags Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Suggestion An idea for TypeScript
#7968 opened Apr 8, 2016 by mattmccutchen
ProTip! Type g i on any issue or pull request to go back to the issue listing page.