We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
yaml-language-server currently uses workspace.symbol.dynamicRegistration to determine whether it registers textDocument/formatting capability.
workspace.symbol.dynamicRegistration
textDocument/formatting
According to the language-server-protocol spec, textDocument.formatting.dynamicRegistration looks appropriate for the purpose.
textDocument.formatting.dynamicRegistration
/** * Text document specific client capabilities. */ export interface TextDocumentClientCapabilities { ... /** * Capabilities specific to the `textDocument/formatting` */ formatting?: { /** * Whether formatting supports dynamic registration. */ dynamicRegistration?: boolean; };
The text was updated successfully, but these errors were encountered:
Yes that should be changed. Is that something you'd like to contribute?
Sorry, something went wrong.
I sent PR. As far as checked, formatting works as previous on VSCode.
Awesome thanks! I'll merge it!
Use textDocument.formatting.dynamicRegistration
ad2d13b
instead of workspace.symbol.dynamicRegistration. redhat-developer/yaml-language-server#74
No branches or pull requests
yaml-language-server currently uses
workspace.symbol.dynamicRegistration
to determine whether it registerstextDocument/formatting
capability.According to the language-server-protocol spec,
textDocument.formatting.dynamicRegistration
looks appropriate for the purpose.The text was updated successfully, but these errors were encountered: