microsoft / microsoft/TypeScript
Support additional trace points
Open
@jakebailey is already working on this.
Since Nov 15, 2021.
Rescheduled
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
Tracing, Logging
Suggestion
In addition to the trace points introduced in #40063, we've had requests for optional tracing of
- inferTypesFrom
- invokeOnce
- getAccessibleSymbolChain
- typeToTypeNode
- getIntersectionType
- getUnionType
- instantiateType
As a result, we will also require a mechanism for indicating which are active in any given run. (Consider mimicking the format used by the debug package.) However, the default should probably remain similar to what's in #40063 since performance analysis is the primary use case.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.