Split ty LSP into a separate plugin - #22
Open
TyceHerrman wants to merge 1 commit into
Open
Conversation
TyceHerrman
marked this pull request as ready for review
July 27, 2026 22:06
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
astralfocused on the uv, ruff, and ty skillsty-lspplugin with the existing ty language-server configurationWhy
The combined plugin always enables the ty language server. Splitting it lets users keep the Astral skills while choosing a different Python language-server plugin.
Closes #16.
Validation
claude plugin validate --strict .claude plugin validate --strict plugins/astralclaude plugin validate --strict plugins/ty-lspprettier --check README.md CONTRIBUTING.mdjq empty .claude-plugin/marketplace.json plugins/astral/.claude-plugin/plugin.json plugins/ty-lsp/.claude-plugin/plugin.jsongit diff --check