Skip to content

docs(triggers): order and breakOnError on trigger saves - #43

Merged
Domantas merged 1 commit into
mainfrom
feat/trigger-order
Oct 8, 2026
Merged

Domantas merged 1 commit into
mainfrom
feat/trigger-order

Conversation

@Domantas

@Domantas Domantas commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

The gateway added two fields to every trigger kind (Schema, Membership, Files, Payments, AI): order (whole number, 0 or more, lower runs first; triggers without an order run after the numbered ones) and breakOnError (true = when this trigger's action fails, the later triggers of the same event are not run). Gateway: codemash-io/gateway refactoringV2 0b218b5e2 (feature) / 251fbc72a.

What changed: the save methods send the caller's map, so the fields already reach the gateway. docs/hub/triggers.md and the README now describe them, with an example.

Tests: new tests/hub/test_trigger_order.py — all four save methods send order (0) and breakOnError in the body. uv run pytest green, make typecheck clean.

🤖 Generated with Claude Code

…test for all four save methods

The gateway added two optional fields to every trigger: order (whole
number, lower runs first) and breakOnError (stop the later triggers of the
same event when this one fails). The save methods send the caller's map, so
the fields already reach the gateway; this documents them and proves it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Domantas
Domantas merged commit 7e43b8a into main Oct 8, 2026
9 checks passed
@Domantas
Domantas deleted the feat/trigger-order branch October 8, 2026 09:11
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