fix(tui): replace stale /connect hints with /provider#303
Merged
Conversation
🦋 Changeset detectedLatest commit: 7d455c7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
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
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.
Related Issue
No related issue. Follow-up cleanup spotted while syncing the 0.7.0 changelog: the
/connectcommand was replaced by/provider, but stale/connectreferences were left behind. See the Problem section.Problem
/connectis no longer a registered slash command (it was replaced by/provider), so invoking it now falls through to "Unknown slash command". Two user-facing hints still told users to run/connect:Following those hints leads users to a command that does not exist. Dead handler code for the old command also remained in the tree.
What changed
/providerinstead of/connect./connectcommand handler, its catalog-argument parser, and that parser's unit test, plus the now-unused re-exports. The handler had no dispatch entry and was unreachable, so this changes no runtime behavior.Verification: typecheck,
oxlint --type-aware(0 errors), the TUI and CLI test suites (853 passing), and the CLI build all pass. Apatchchangeset is included.Checklist
gen-changesetsskill, or this PR needs no changeset. — Added apatchchangeset for@moonshot-ai/kimi-code.gen-docsskill, or this PR needs no doc update. — The docs already document/provider; no current-command reference to/connectremains.