Render ConfigKit show and validate through reporter
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Invocation reporting implementation plan
|
||||
|
||||
Status: Stages 1–10 complete. Stage 11 is next.
|
||||
Status: Stages 1–11 complete. Stage 12 is next.
|
||||
|
||||
## Objective and authority
|
||||
|
||||
@@ -418,7 +418,7 @@ migration; Stage 20 will validate the assembled modules.
|
||||
|
||||
## Stage 11: Migrate configuration show and validate
|
||||
|
||||
Status: pending.
|
||||
Status: complete.
|
||||
|
||||
Primary files: [show.go](../../integrations/ckconfig/show.go),
|
||||
[validate.go](../../integrations/ckconfig/validate.go), and
|
||||
@@ -449,6 +449,15 @@ deferred context ordering, rendering failures, and report write failures.
|
||||
Update tests of superseded outcome fields to observable reports and
|
||||
`Presentation`, rather than dropping their original failure protection.
|
||||
|
||||
Configuration show and validate now submit provider messages through the shared
|
||||
reporter and render results through managed output. Tests retain acquisition
|
||||
ordering, shared state, YAML framing, cancellation with partial validation
|
||||
output, and cover warning visibility, terminal context, quiet rendering, and
|
||||
destination failures through `Presentation`. The ckconfig tests remain
|
||||
unrunnable because `sources.go`, `explain.go`, `diff.go`, and family wiring and
|
||||
tests still reference APIs scheduled for later migrations; Stage 20 will run the
|
||||
assembled suites.
|
||||
|
||||
## Stage 12: Migrate configuration sources, explain, and diff
|
||||
|
||||
Status: pending.
|
||||
|
||||
Reference in New Issue
Block a user