Ryan Cavanaugh
Ryan Cavanaugh
[api-extractor] API report shows spurious diffs because compiler emits inferred types inconsistently
Relevant things that could happen to my knowledge: * Union types are printed in an arbitrary order * Type aliases may or may not be used to represent equivalent types...
[api-extractor] API report shows spurious diffs because compiler emits inferred types inconsistently
Yeah, if we're able to re-use the existing text of a node, we always will
This open source software [is provided "as-is"](https://github.com/microsoft/tslib/blob/main/LICENSE.txt#L6) and does not have an explicit or implied support cycle that would inform an "end of life" date. Development and maintenance is currently...
We need a (reasonably small) repro
Why are design limitations closed -> https://github.com/Microsoft/TypeScript/wiki/FAQ#this-is-closed-but-should-be-open-or-vice-versa
GitHub added the "*why* was this closed (completed/not done)" bit after we closed a bunch of stuff, and auto-marked a bunch of stuff as "completed" as a result. Also for...
Omnibus tracked at #47599. An alternative workaround is to write ```ts foo: () => { return 1; }, ```