Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support additional trace points #40460

Open
7 tasks
amcasey opened this issue Sep 9, 2020 · 0 comments
Open
7 tasks

Support additional trace points #40460

amcasey opened this issue Sep 9, 2020 · 0 comments
Assignees
Labels
Rescheduled This issue was previously scheduled to an earlier milestone

Comments

@amcasey
Copy link
Member

amcasey commented Sep 9, 2020

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.

@amcasey amcasey added this to the TypeScript 4.1.0 milestone Sep 9, 2020
@RyanCavanaugh RyanCavanaugh added the Rescheduled This issue was previously scheduled to an earlier milestone label Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rescheduled This issue was previously scheduled to an earlier milestone
Projects
None yet
Development

No branches or pull requests

6 participants