Expand ServerCapabilities to the full spec field set#11
Merged
Conversation
ServerCapabilities previously exposed only positionEncoding. Add the documented provider/capability fields from the LSP initialize spec: sync, completion, hover, definition, references, formatting, rename, code actions/lens, semantic tokens, diagnostics, workspace, experimental and the rest. Following this module's convention, dedicated XxxOptions objects are typed as dict and `boolean | XxxOptions` unions as bool|dict. Also add the TextDocumentSyncKind enum used by textDocumentSync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
christiankissig
added a commit
that referenced
this pull request
Jul 7, 2026
Expand ServerCapabilities to the full spec field set
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fleshes out
ServerCapabilitiesper LSP 3.17 — Initialize. It previously exposed onlypositionEncoding; this adds the full documented set of provider/capability fields returned in theInitializeResult.Changes
ServerCapabilitiesnow includes every field from the spec:textDocumentSync,notebookDocumentSync,completionProvider,hoverProvider,signatureHelpProvider, the goto providers (declaration/definition/typeDefinition/implementation),referencesProvider,documentHighlightProvider,documentSymbolProvider,codeActionProvider,codeLensProvider,documentLinkProvider,colorProvider, formatting providers,renameProvider,foldingRangeProvider,executeCommandProvider,selectionRangeProvider,linkedEditingRangeProvider,callHierarchyProvider,semanticTokensProvider,monikerProvider,typeHierarchyProvider,inlineValueProvider,inlayHintProvider,diagnosticProvider,workspaceSymbolProvider,workspace, andexperimental.TextDocumentSyncKindenum added (None_=0,Full=1,Incremental=2), used bytextDocumentSync.Typing convention
Consistent with the rest of
protocol.py(where nested capability structures aredict | None):boolean | XxxOptions→bool | dict | None,XxxOptions/XxxRegistrationOptions→dict | None,textDocumentSync→TextDocumentSyncKind | dict | None.All fields default to
None, so the existing minimal-ServerCapabilitiesbehaviour (andmodel_dump(exclude_none=True)) is unchanged — fully backward compatible.Testing
TextDocumentSyncKindvalues, mixed provider serialisation (enum + bool + options dicts),textDocumentSyncas an options object, and parsing a realistic server response payload viamodel_validate.poetry run pytest(75 passed),ruff check,ruff format --check, andmypyall clean.🤖 Generated with Claude Code