Skip to content

Conversation

@orta
Copy link
Contributor

@orta orta commented Nov 20, 2020

I think this should unblock #41262 - the param format? was introduced to the tsserver API in #38435 . In order to be used by vscode, it needs to be exposed via the session.ts and protocol.ts.

Which is what this PR does, it also adds some extra values to some of the types in the protocol.

@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

@typescript-bot typescript-bot added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Nov 20, 2020
@orta
Copy link
Contributor Author

orta commented Nov 20, 2020

Thanks sheetal!

@orta orta merged commit 9d25e59 into microsoft:release-4.1 Nov 20, 2020
@sheetalkamat
Copy link
Member

May be we need this for 4.1 patch as well ?

/**
* Optional for backwards compat, use "2020" for modern LSP-like classifications
*/
format?: ts.SemanticClassificationFormat
Copy link
Contributor

@mjbvz mjbvz Nov 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@orta Just want to check that this will also update the protocol.d.ts file that we consume. I didn't see the semantic APIs in the d.ts when I last checked

@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

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants