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
While it is helpful to have the error reporter give precise context on why TypeScript introduces an error (or what led up to its crash), it would be much easier for us if we could get a minimal repro of code to quickly understand what changed, and in the case of crashes, what's the number of commands to hit the crash.
We wouldn't necessarily want this on every run (this could take some time). @armanio123 has already mentioned maybe this can be toggled only for specific runs and done on our weekly runs.
The text was updated successfully, but these errors were encountered:
While it is helpful to have the error reporter give precise context on why TypeScript introduces an error (or what led up to its crash), it would be much easier for us if we could get a minimal repro of code to quickly understand what changed, and in the case of crashes, what's the number of commands to hit the crash.
We wouldn't necessarily want this on every run (this could take some time). @armanio123 has already mentioned maybe this can be toggled only for specific runs and done on our weekly runs.
The text was updated successfully, but these errors were encountered: