Skip to content

Preserve CLI API filter output and page metadata - #37

Merged
purpshell merged 1 commit into
devfrom
codex/api-output-rough-edges
Sep 26, 2026
Merged

purpshell merged 1 commit into
devfrom
codex/api-output-rough-edges

Conversation

@purpshell

@purpshell purpshell commented Sep 26, 2026 •

Copy link
Copy Markdown
Member

polymorfa api lost leading and trailing whitespace from --jq string results, closed template actions at }} inside quoted strings, and dropped per-page metadata when --paginate --slurp --include was used. The command now preserves each jq string value, scans quoted template actions and comments correctly, and includes each page's response metadata in collected human output.

The command help and README describe the resulting output shapes. Public Mintlify guidance is prepared in polymorfa/polymorfa#350; that PR must remain unmerged until the CLI package is published for the documented audience.

API: unaffected; request paths, authentication, wire data, and cursor behavior are unchanged. SDKs: unaffected; the CLI uses the existing @polymorfa/sdk raw client contract. CLI: updated in src/api/jq.ts, src/api/template.ts, src/commands/api.ts, focused command tests, and README. Docs: updated in this README and the companion public docs PR. Feature release: no new flag, entitlement, or API release stage; these are output fixes. CLI npm publication and customer availability remain separate release gates.

Validation: focused template and command tests (23 passed), typecheck, lint, format check, build, and live api --help output. Exact-head Node 22 CI passed. A local full run with --maxWorkers=2 had 22 failures across unrelated command files while other agent test processes were active; no api tests failed. The SIGINT and SIGTERM unread-pipe tests each timed out after about 5 seconds with AbortError: The operation was aborted. On a clean origin/dev worktree (fad2cf7) with the same worker setting, the isolated SIGINT pipe test reproduced that timeout; a later full baseline run passed all 856 tests. These results point to host-load sensitivity, and I stopped broad local reruns.

@coderabbitai

coderabbitai Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 12 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 63 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 61fc8fcd-057f-420e-8fde-86fb2efd785e

📥 Commits

Reviewing files that changed from the base of the PR and between 82c9726 and 79eefc9.

📒 Files selected for processing (6)
  • README.md
  • src/api/jq.ts
  • src/api/template.ts
  • src/commands/api.ts
  • test/api/template.test.ts
  • test/commands/api-gh.test.ts

Comment @coderabbitai help to get the list of available commands.

@purpshell
purpshell force-pushed the codex/api-output-rough-edges branch from 5898ff1 to 79eefc9 Compare September 26, 2026 10:39
@purpshell
purpshell merged commit 0982f48 into dev Sep 26, 2026
3 checks passed
@purpshell
purpshell deleted the codex/api-output-rough-edges branch October 26, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant