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
In our legacy project, we've started using TypeScript and have also created a jsconfig to start validating our JavaScript files.
Unfortunately we have a long way to go, and a jsconfig -p jsconfig.json shows ~5000 errors..
We still would like to get the benefit of using a jsconfig and hence it has been useful that these errors and shown in the editor so that a dev can consider to fix them. However, since the errors are shown with a red line, it is now quite difficult for a developer to distinguish between eslint errors (which break a build) and ts errors.
While the TS errors provide good tips and suggested improvements, for our codebase they aren't really errors, but rather warnings and I'm missing the option to show them as yellow squiggly lines. Would be awesome if this became a part of VSCode!
I.e. something along the lines of javascript.implicitProjectConfig.errorType: "warnings".
To illustrate the issue here is a file:
The text was updated successfully, but these errors were encountered:
In our legacy project, we've started using TypeScript and have also created a
jsconfig
to start validating our JavaScript files.Unfortunately we have a long way to go, and a
jsconfig -p jsconfig.json
shows ~5000 errors..We still would like to get the benefit of using a jsconfig and hence it has been useful that these errors and shown in the editor so that a dev can consider to fix them. However, since the errors are shown with a red line, it is now quite difficult for a developer to distinguish between eslint errors (which break a build) and ts errors.
While the TS errors provide good tips and suggested improvements, for our codebase they aren't really errors, but rather warnings and I'm missing the option to show them as yellow squiggly lines. Would be awesome if this became a part of VSCode!
I.e. something along the lines of
javascript.implicitProjectConfig.errorType: "warnings"
.To illustrate the issue here is a file:
The text was updated successfully, but these errors were encountered: