Skip to content

Try to create minimal reproductions of new errors, possibly crashes #164

Open
@DanielRosenwasser

Description

@DanielRosenwasser

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.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions