Repository navigation
fix(list): validate --limit and add ft waitlist (contract 1.24) - #51
Conversation
--limit 500 o --limit abc llegaban a la API y volvían en silencio con la página por defecto de 20. parseLimit() falla con exit 1 y un mensaje claro; aplicado en resource list, admin list y api-keys list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fo7cm6n2VPy94zeSbmhgt8
Sincroniza openapi.json a 1.24.0 y cablea GET/POST /waitlist, el unico endpoint B2B del spec de prod que el CLI no exponia. `list` filtra con --city y hereda --workspace/--account/--all/--csv del patron resource. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fo7cm92jLJxUttSHQHWMAk
PR Summary by QodoValidate list limits and add waitlist commands for API 1.24
AI Description
Diagram
High-Level Assessment
Files changed (11)
|
What changes
--limitis now validated (integer 1-100). Previously--limit 500|abc|0reached the API and silently returned the default page of 20.allocations[].amount/mode).ft waitlist list|create, the only production B2B endpoint that had no command.Flow diagram
flowchart LR A[ft ... --limit N] --> B{parseLimit 1-100} B -- invalid --> C[exit 1 + message] B -- ok --> D[/api/v1/]How to test
🤖 Generated with Claude Code