Skip to content

Export ProgressToken from the package root#12

Merged
christiankissig merged 1 commit into
masterfrom
export-progress-token
Jun 4, 2026
Merged

Export ProgressToken from the package root#12
christiankissig merged 1 commit into
masterfrom
export-progress-token

Conversation

@christiankissig

Copy link
Copy Markdown
Owner

Summary

ProgressToken is defined in lsp_client/protocol.py and is part of the public API — ProgressParams, WorkDoneProgressCreateParams, and WorkDoneProgressCancelParams all type their token field with it — but it was missing from the package __init__. As a result from lsp_client import ProgressToken raised ImportError.

This adds ProgressToken to both the __init__ imports and __all__, filling a gap left by the recent server-capabilities expansion.

Why

Downstream code (e.g. the Isabelle LSP client) needs to import ProgressToken to annotate work-done-progress handling. Without this export it has to re-declare the alias locally, duplicating a spec type.

Test plan

  • ruff check clean
  • pytest — 75 passed

🤖 Generated with Claude Code

ProgressToken is defined in protocol.py and is part of the public surface
(ProgressParams, WorkDoneProgressCreateParams and WorkDoneProgressCancelParams
all expose it), but it was missing from the package __init__, so
`from lsp_client import ProgressToken` failed. Add it to the imports and __all__.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@christiankissig christiankissig merged commit 634421c into master Jun 4, 2026
7 checks passed
@christiankissig christiankissig deleted the export-progress-token branch June 4, 2026 06:57
christiankissig added a commit that referenced this pull request Jul 7, 2026
Export ProgressToken from the package root
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant