You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One consistent piece of feedback from users who have been using Visual Studio long-term to develop JavaScript-only projects is that the old, execution-based language service in Visual Studio 2015 did a better job picking up certain common JavaScript patterns than the TypeScript language service.
This is a meta-issue to collect specific instances where TypeScript didn't do as good a job as VS 2015 IntelliSense. By targeting these specific fixes we hope to improve the experience of users upgrading from VS 2015, as well as improve our type inference for pure JavaScript in general.
DanielRosenwasser
changed the title
[meta] Improve pure JavaScript language service support
Language service support for classic JavaScript patterns meta-issue
Aug 12, 2020
One consistent piece of feedback from users who have been using Visual Studio long-term to develop JavaScript-only projects is that the old, execution-based language service in Visual Studio 2015 did a better job picking up certain common JavaScript patterns than the TypeScript language service.
This is a meta-issue to collect specific instances where TypeScript didn't do as good a job as VS 2015 IntelliSense. By targeting these specific fixes we hope to improve the experience of users upgrading from VS 2015, as well as improve our type inference for pure JavaScript in general.
this
not treated as a constructor Function declaration with aliasedthis
not treated as a constructor #39842@description
JSDoc tag interferes with callback parameter documentation @description JSDoc tag interferes with callback parameter documentation #37346The text was updated successfully, but these errors were encountered: