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
{{ message }}
Repository navigation
Suggestion : Add a compiler flag to treat errors as warnings #14501
That will allows to compile asp.net web project in VS without compile errors.
For now the build is fail. We have the legacy asp.net project . We started migration from js to ts. In the first stage we renamed all js files to ts. There are a lot typescript errors, but generated js is still valid.
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.
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.
Any news on this?
How can i just compile even on error? We are migrating from js to ts.
I have a lot of file just renamed to .ts waiting to be converted.
If i compile on save, i have the error in the error list but the js file is emitted.
Instead msbuild stop on the error and that broke my CI in teamcity.
Why i can't replicate this behavior in msbuild? I can't flag 2000+ lines with // ts-ignore
Activity
RyanCavanaugh commentedon Mar 7, 2017
Other than printing
instead of
what would you expect this flag to do, behaviorally?
ifle commentedon Mar 8, 2017
That will allows to compile asp.net web project in VS without compile errors.
For now the build is fail. We have the legacy asp.net project . We started migration from js to ts. In the first stage we renamed all js files to ts. There are a lot typescript errors, but generated js is still valid.
mribichich commentedon May 30, 2017
Same for me, I have a couple of errors that I know there ok, but since typescript treats them as errors the build fails.
mhegazy commentedon May 30, 2017
what are the errors if i may ask?
onzag commentedon Sep 18, 2017
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.
mhegazy commentedon Sep 18, 2017
what is your build driver? MSBuild?
aminpaks commentedon Oct 21, 2017
I think the new compiler
@ts-ignoreflag will cover this no?ifle commentedon Oct 21, 2017
That is right direction :). In my case the best solution is adding the flag to the tsconfig with optional list of ignored errors
aminpaks commentedon Oct 21, 2017
ifle (@ifle) apparently the topic is more complicated that I thought. Read what Alex Eagle (@alexeagle) has to say about this
alexeagle commentedon Oct 22, 2017
I agree, for violations of the type system or language spec,
// @ts-ignoregives you an extra freedom to disable errors during a migration.KodaPOwER commentedon Jan 10, 2018
Any news on this?
How can i just compile even on error? We are migrating from js to ts.
I have a lot of file just renamed to .ts waiting to be converted.
If i compile on save, i have the error in the error list but the js file is emitted.
Instead msbuild stop on the error and that broke my CI in teamcity.
Why i can't replicate this behavior in msbuild? I can't flag 2000+ lines with // ts-ignore
bodinsamuel commentedon Jul 17, 2019
Hello, It's a been long time and the issue is not closed.
Is it something you are planning? thanks :)
RyanCavanaugh commentedon Jul 17, 2019
I think the only thing left to address here is the msbuild scenario, which is effectively tracked at #13280
QingLeiLi commentedon Oct 20, 2019
Maybe we should add a ts config option to prevent the error to throw.
nbkhope commentedon Apr 29, 2022
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.
TomasHubelbauer commentedon Feb 3, 2023
Would be cool to be able to treat unused imports as errors.