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
For VS Code, we'd like the ability for VSCode settings to control the behavior of a TS Server plugin. For example, we'd like to pass a setting like "css.lint.emptyRules": "warning" from VSCode to a TypeScript CSS plugin that is contributed by a vscode extensions
There is currently no way for a host client like VSCode to communicate with a TSServer plugin. Plugins may take an optional configuration in the tsconfig.json, but this is static information that the user must enter. If no tsconfig exists, one must be created.
Proposal
Introduce a new TSServer call named configurePlugin or something similar. This call would take a plugin name and a configuration object:
On TSServer plugins, introduce a new hook called onPluginConfigurationChanged or something similar. This hook would be invoked with the configuration object:
Problem
For VS Code, we'd like the ability for VSCode settings to control the behavior of a TS Server plugin. For example, we'd like to pass a setting like
"css.lint.emptyRules": "warning"
from VSCode to a TypeScript CSS plugin that is contributed by a vscode extensionsThere is currently no way for a host client like VSCode to communicate with a TSServer plugin. Plugins may take an optional configuration in the
tsconfig.json
, but this is static information that the user must enter. If no tsconfig exists, one must be created.Proposal
Introduce a new TSServer call named
configurePlugin
or something similar. This call would take a plugin name and a configuration object:On TSServer plugins, introduce a new hook called
onPluginConfigurationChanged
or something similar. This hook would be invoked with the configuration object:The text was updated successfully, but these errors were encountered: