-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Suggestion : Add a compiler flag to treat errors as warnings #14501
Comments
Other than printing a.ts(12,12): warning TS2345 instead of a.ts(12,12): error TS2345 what would you expect this flag to do, behaviorally? |
That will allows to compile asp.net web project in VS without compile errors. |
Same for me, I have a couple of errors that I know there ok, but since typescript treats them as errors the build fails. |
what are the errors if i may ask? |
How is this going, I have thousand of errors because I am running a migration, but the build fails because of the errors, giving a lot of log messages in webpack, I simply can't fix them all. |
what is your build driver? MSBuild? |
I think the new compiler |
That is right direction :). In my case the best solution is adding the flag to the tsconfig with optional list of ignored errors |
@ifle apparently the topic is more complicated that I thought. Read what @alexeagle has to say about this |
I agree, for violations of the type system or language spec, |
Any news on this? |
Hello, It's a been long time and the issue is not closed. |
I think the only thing left to address here is the msbuild scenario, which is effectively tracked at #13280 |
Maybe we should add a ts config option to prevent the error to throw. |
Was this feature ever implemented? I too would love to have errors be just warnings as it helps migrating a codebase from JS to TS. |
Would be cool to be able to treat unused imports as errors. |
Add a compiler flag to treat errors as warnings.
That will be very helpful in case of migration from legacy javascript project to typescript
The text was updated successfully, but these errors were encountered: