Skip to content

Conversation

@amcasey
Copy link
Member

@amcasey amcasey commented Feb 4, 2020

I made it internal because I wasn't expecting to have external consumers (and it's a safe default). Should things like this be public (e.g. if VS Code is going to consume them)?

Fixes #36589

@typescript-bot
Copy link
Collaborator

Thanks for the PR! It looks like you've changed the TSServer protocol in some way. Please ensure that any changes here don't break consumers of the current TSServer API. For some extra review, we'll ping @sheetalkamat, @amcasey, @mjbvz, @minestarks for you. Feel free to loop in other consumers/maintainers if necessary

@amcasey amcasey marked this pull request as ready for review February 4, 2020 21:05
@amcasey
Copy link
Member Author

amcasey commented Feb 4, 2020

@mjbvz Are you asking for this for 3.8?

@mjbvz
Copy link
Contributor

mjbvz commented Feb 4, 2020

@amcasey It'd be nice to have but we can work around it

@amcasey amcasey merged commit 2e97918 into microsoft:master Feb 4, 2020
@amcasey
Copy link
Member Author

amcasey commented Feb 4, 2020

@typescript-bot cherry-pick this to release-3.8

@amcasey amcasey deleted the PublicPerfData branch February 4, 2020 23:09
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

performanceData.updateGraphDurationMs missing from protocol.d.ts

5 participants