You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a lot of providers [e.g. DocumentSemanticTokensProvider] supports a single one. if multiple are registered the best matching one is chosen.
So no 2nd extension can add tokens along with 1st extension's tokens.
The Feature
Add support for multiple SemanticTokensProvider, [possibly other providers too].... so that, a extension can add stuffs on top of another.
Some may ask, 'Why?'. Bcz semanticTokens are more like for IntelliSense, and running multiple different IntelliSense is not a good performance Idea.
But, there could be a single running Intellisense & LanguageServer that two different extensions could be using, and both of those could be like adding different kinds of SemanticTokens....
The text was updated successfully, but these errors were encountered:
REYNEP
changed the title
Add support for multiple SemanticTokensProvider, [possibly other providers too].... so that, a extension can add stuffs on top of another
Add support for multiple SemanticTokensProvider, [possibly other providers too]
Oct 21, 2021
Currently a lot of providers [e.g.
DocumentSemanticTokensProvider
] supports a single one. if multiple are registered the best matching one is chosen.The Feature
Add support for multiple
SemanticTokensProvider
, [possibly other providers too].... so that, a extension can add stuffs on top of another.Some may ask, 'Why?'. Bcz semanticTokens are more like for IntelliSense, and running multiple different IntelliSense is not a good performance Idea.
The text was updated successfully, but these errors were encountered: