Conversation
Applies the router's help-group mechanism (#2262) to the seven gateway commands whose flat option lists had grown past skimming. Presentation only — no flag is added, removed, or renamed, and no request changes. - connector create: Target, Connector, Credentials & networking - connector update: + Clear (unset a field) for the --clear-* flags - create: Configuration, Protocol, Authorizer, Interceptors, Policy engine - invoke: Target, Payload, Authentication, Application headers, Session - target create: Target, Definition, Credentials & networking, Idempotency - target update: Target, Definition, Credentials & networking, Clear (unset a field) - update: Target, Configuration, Protocol & authorizer, Transform & interceptors, Policy engine, WAF, Clear (unset a field) create, invoke, and update reorder their flags so each heading's flags declare contiguously (Commander orders headings by first-declared flag); the update commands collect their --clear-* flags under one heading. A command that groups its flags gets its generated -h/--help moved to "Other options:".
|
Claude Security Review: no high-confidence findings. (run) |
There was a problem hiding this comment.
AgentCore Harness Review
Verdict: Looks good
This is a pure UX refactor that assigns existing gateway-command flags to help groups via the flag() factory's existing group option. The plumbing (option.helpGroup in src/router/flags.tsx and the group rendering in src/components/CliOnlyScreen.tsx) already exists, so this just improves --help organization with no runtime behavior change.
Things I checked:
- Every flag in each touched file has been assigned a group — no stragglers.
- Group label strings are consistent across files:
"Target:","Configuration:","Credentials & networking:","Clear (unset a field):","Policy engine:","Connector:","Definition:", etc. all agree wherever they appear. - No schema, handler logic, or I/O boundaries changed, so tests and telemetry are unaffected. Telemetry is not needed for a help-text-only change.
Minor style-only nits I'll flag but wouldn't block on:
- In
src/handlers/gateway/update/index.tsx,iduses inline"Target:"andinterceptor-configurationsuses inline"Interceptors:"while sibling flags useconstlabels (CONFIGURATION,POLICY_ENGINE,TRANSFORM,CLEAR). Same pattern ingateway/create/index.tsx("Interceptors:") andgateway/target/create/index.tsx("Idempotency:"). Optional to normalize on the const style for consistency.
LGTM to merge.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## refactor #2304 +/- ##
==========================================
Coverage 96.98% 96.99%
==========================================
Files 579 579
Lines 39442 39565 +123
==========================================
+ Hits 38253 38376 +123
Misses 1189 1189 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Applies the router's help-group mechanism from #2262 to the seven
gatewaycommands whose flat option lists had grown past skimming. Presentation only — no flag is added, removed, or renamed, and no request changes.gateway connector creategateway connector updategateway creategateway invokegateway target creategateway target updategateway updateNotes
create,invoke, andupdatereorder their flags so each heading's flags declare contiguously (Commander orders headings by first-declared flag).updatemoves--exception-levelup into Configuration.updatecommands collect their--clear-*flags under oneClear (unset a field):heading.-h/--helpmoved toOther options:.Testing
bun run typecheckcleanbun run lintcleanbun test src/handlers/gateway— 226 passProposed
--helpagentcore gateway connector create --helpagentcore gateway connector update --helpagentcore gateway create --helpagentcore gateway invoke --helpagentcore gateway target create --helpagentcore gateway target update --helpagentcore gateway update --help