Repository navigation
Add Messaging campaign update command - #42
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Adds
polymorfa campaign update CAMPAIGN_ID --project-slug SLUG --input patch.jsonfor the Messaging PATCH contract in API #332. It sends a typed SDK request with only the four editable fields, rejects an empty or unsupported JSON patch before transport, prints the campaign, and returns a conflict without replaying the write.This is a draft until SDK #307 is merged and its exact version and integrity are verified in the npm registry. The committed dependency and lockfile still pin the older published SDK, so registry-based CI cannot typecheck
campaigns.updateyet. The command was tested locally against SDK #307 source with a temporary untrackednode_modulessymlink; no local-path dependency is committed. Before merge, pin the verified registry version, regenerate the lockfile, and rerun exact-head CI.Six-part impact: API #332 owns the handler, auth/scope, OpenAPI and errors; SDK #307 owns the typed method/request; CLI command/service/help and JSON/conflict tests are changed here; README and API Mintlify guide/reference cover usage, while public SDK docs must not claim unpublished availability; the API release record remains unreleased pending SDK/CLI publication, deployment, and live acceptance; Admin controls are unaffected because this project-scoped customer edit grants no staff operation.
Local validation against SDK #307: 18 focused command tests, CLI lint, typecheck, build, and format check passed. Registry-based CI and publication remain pending. No deployed endpoint was exercised.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.