Skip to content

feat(payments): every Payments endpoint has a command - #80

Merged
Domantas merged 2 commits into
mainfrom
feat/payments-commands
Oct 15, 2026
Merged

Domantas merged 2 commits into
mainfrom
feat/payments-commands

Conversation

@Domantas

Copy link
Copy Markdown
Contributor

Every Payments endpoint a person calls now has a command (COVERAGE payments 7/16 → 17/17):

  • payments enable|disable — the Payments module (same as sms / email).
  • payments integration <id> | save | test | confirm-delivery | enable | disable | delete.
  • payments trigger save (JSON file; type: Payments, when: OnWebhookCallReceived filled in; --event / --integration / --order / --break-on-error) | enable | disable | delete.
  • payments webhook-log [--integration] [--limit ≤200] — the provider webhooks the project received.

Breaking: up to 1.33, payments enable|disable <id> turned a trigger on or off; that is now payments trigger enable|disable <id>. The old form fails with exit 2, sends nothing, and its hint names the new command. Shipped as a minor release; the old form was a one-word trigger toggle with no known scripted users.

Also: @norbix.ai/ts 4.28.0. gen:fields now accepts a @deprecated forwarder that calls the other host. In 4.28.0 those are hub.notifications.grantContactConsent / unsubscribeContact.

Tests: vitest run 37 files / 1026 passed. The new tests/payments-routes.test.ts checks the verb and path of every command, plus the bodies. tsc --noEmit is clean. Docs: docs/payments.md.

Gateway campaign audit/payments (codemash-io/gateway), item 9. Expected release: minor.

🤖 Generated with Claude Code

Domantas and others added 2 commits October 15, 2026 14:26
…s-host forwarder through

4.28.0 keeps hub.notifications.grantContactConsent / unsubscribeContact as
@deprecated forwarders to the API route. gen:fields reported them as a
wrong-host problem; a method whose doc says @deprecated may now call the other
host. A non-deprecated method on the wrong host is still a problem.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… triggers, webhook log

- payments enable|disable: the Payments module (like sms / email).
- payments integration <id> | save | test | confirm-delivery | enable | disable | delete.
- payments trigger save (from a JSON file; type Payments and when
  OnWebhookCallReceived filled in; --event / --integration / --order /
  --break-on-error) | enable | disable | delete.
- payments webhook-log: the provider webhooks the project received.

Breaking: up to 1.33 `payments enable|disable <id>` toggled a trigger; that is
now `payments trigger enable|disable <id>`. The old form fails with exit 2,
sends nothing, and its hint names the new command.

tests/payments-routes.test.ts runs all 17 commands through the real transport
(verb + path) and checks the save / test / log / toggle bodies. docs/payments.md;
COVERAGE payments 7/16 → 17/17.

Gateway campaign audit/payments (codemash-io/gateway), item 9.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Domantas
Domantas merged commit 8b770c8 into main Oct 15, 2026
11 checks passed
@Domantas
Domantas deleted the feat/payments-commands branch October 15, 2026 11:35
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.34.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant