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

Option to show TS errors as warnings in JavaScript files #29810

Closed
anton164 opened this issue Feb 7, 2019 · 2 comments
Closed

Option to show TS errors as warnings in JavaScript files #29810

anton164 opened this issue Feb 7, 2019 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@anton164
Copy link

anton164 commented Feb 7, 2019

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:
screenshot 2019-02-07 at 12 26 47

@vscodebot vscodebot bot assigned mjbvz Feb 7, 2019
@mjbvz mjbvz transferred this issue from microsoft/vscode Feb 7, 2019
@mjbvz mjbvz removed their assignment Feb 7, 2019
@mjbvz
Copy link
Contributor

mjbvz commented Feb 7, 2019

Possibly falls under #13408

@RyanCavanaugh RyanCavanaugh added the Duplicate An existing issue was already created label Feb 14, 2019
@typescript-bot
Copy link
Collaborator

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

4 participants