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
We are migrating a legacy codebase from JS to TS, and currently there are many thousands of errors. When we edit a given file, we usually use the VS Code Problems Pane to ensure that there are no errors left in the file we've edited. But when we change a component/function that's used in many places, it's difficult to ensure that we haven't added type errors in those other places.
Will this action help us with that? Is there some kind of reporting of "total number of errors", especially compared with the main branch? Can it highlight newly-added errors on non-changed files?
I imagine these are very difficult things to build if you do not already have the functionality (namely, comparing to the main branch's latest results). But I thought I'd ask as it might be very helpful.
The text was updated successfully, but these errors were encountered:
We are migrating a legacy codebase from JS to TS, and currently there are many thousands of errors. When we edit a given file, we usually use the VS Code Problems Pane to ensure that there are no errors left in the file we've edited. But when we change a component/function that's used in many places, it's difficult to ensure that we haven't added type errors in those other places.
Will this action help us with that? Is there some kind of reporting of "total number of errors", especially compared with the main branch? Can it highlight newly-added errors on non-changed files?
I imagine these are very difficult things to build if you do not already have the functionality (namely, comparing to the main branch's latest results). But I thought I'd ask as it might be very helpful.
The text was updated successfully, but these errors were encountered: