Migrate core to the vanity module path

This commit is contained in:
2026-11-04 03:49:38 +00:00
parent 881dae27c4
commit e256eb1cc0
48 changed files with 120 additions and 87 deletions

View File

@@ -24,8 +24,10 @@ Bash. Build it with the basename shown above, load
the script for your shell using the [CLI reference](../../docs/cli.md#shell-completion),
and try completing `core-example report d` or `core-example ws gr`.
Integration factories also return `commandkit.Command` and can be passed
directly to `New` beside `commandkit.Alias` or flag-alias declarations. For a
Compatible integration factories also return `commandkit.Command` and can be
passed directly to `New` beside `commandkit.Alias` or flag-alias declarations.
The current integrations still use the old core identity; the planned matched
vanity-path releases will use the new core identity. For a
command-only `[]commandkit.Command`, convert its elements into a
`[]commandkit.Declaration` before appending routing rules; Go cannot expand the
command slice as `...commandkit.Declaration`. The
@@ -33,7 +35,5 @@ command slice as `...commandkit.Declaration`. The
shows both forms, and the [composed consumer](../../integrations/ckprompt/examples/composed)
is the maintained integration example.
These aliases use the current local CommandKit source. Published CommandKit
v0.2.0 does not include alias declarations; consumers can use them after the
next core release. Repository contributors can run its test with
These aliases require core v0.3.0. Repository contributors can run its test with
`go test ./examples/core` from the root.

View File

@@ -8,7 +8,7 @@ import (
"os"
"strconv"
commandkit "gitea.maximumdirect.net/eric/CommandKit"
commandkit "go.maximumdirect.net/commandkit"
)
type greetInput struct {

View File

@@ -8,7 +8,7 @@ import (
"strings"
"testing"
commandkit "gitea.maximumdirect.net/eric/CommandKit"
commandkit "go.maximumdirect.net/commandkit"
)
func TestAliasesReachCoreExampleCommand(t *testing.T) {