2.3 KiB
CommandKit ckconfig v0.2.0
Summary
CommandKit ckconfig v0.2.0 moves the integration to
go.maximumdirect.net/ckconfig and uses go.maximumdirect.net/commandkit v0.3.0
with ConfigKit v0.8.0. It adopts core's invocation reporting and completion
contracts while retaining ConfigKit-owned inspection and comparison behavior.
Migration
Replace imports of gitea.maximumdirect.net/eric/CommandKit/integrations/ckconfig
with go.maximumdirect.net/ckconfig, and update core imports to
go.maximumdirect.net/commandkit. Select ckconfig v0.2.0 and core v0.3.0
as a matched set. Old and new core paths have distinct Go type identities.
Applications also using PromptKit should move to the forthcoming matched
go.maximumdirect.net/ckprompt v0.2.0 release.
Handlers use Invocation.Reporter() for output and categorized messages;
terminal failures carry an explanation and optional cause. The integration
submits provider diagnostics through the invocation reporter, respecting shared
reporting flags. Update callers that used Invocation.Streams,
Outcome.Diagnostics, or the old error-first failure API as described in the
core migration guide.
The standard config commands also provide completion hints for applicable
selectors and file paths when the application installs core's completion command.
Go 1.26.0 remains the consumer minimum. Importing ckconfig does not install
commands; pass its declarations to commandkit.New or App.Register.
See the module README
and consumer guide.