You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -329,7 +329,6 @@ Two abstraction levels exist for list commands:
329
329
330
330
Key rules when writing overrides:
331
331
- Each mode handler receives a `HandlerContext<T>` with the narrowed `parsed` plus shared I/O (`stdout`, `cwd`, `flags`). Access parsed fields via `ctx.parsed.org`, `ctx.parsed.projectSlug`, etc. — no manual `Extract<>` casts needed.
332
-
- When multiple modes share one handler, use the `fallback` option instead of repeating the handler for each key: `fallback: (ctx) =>sharedHandler({ ...ctx, extra })`.
333
332
- Commands with extra fields (e.g., `stderr`, `setContext`) spread the context and add them: `(ctx) =>handle({ ...ctx, flags, stderr, setContext })`. Override `ctx.flags` with the command-specific flags type when needed.
334
333
- `resolveCursor()` must be called **inside** the `org-all` override closure, not before `dispatchOrgScopedList`, so that `--cursor` validation errors fire correctly for non-org-all modes.
335
334
- `handleProjectSearch` errors must use `"Project"` as the `ContextError` resource, not `config.entityName`.
0 commit comments