docs(intent): notify.forEach - one message per related row (#6356) - #155
Merged
Conversation
Fan a notify block out over a related collection: one message per row, with the recipient, the placeholders and attach: print all resolving against the ROW. Records the exactly-one-back-reference rule and the fail-soft-per-row contract (a retry would resend to everyone already served).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #154, documenting the fan-out added in eclipse-dirigible/dirigible#6435.
forEach:fans a notify block out over a related collection - one message per row, with the recipient, the{placeholders}andattach: printall resolving against the row. The motivating case is a payroll run mailing every payslip to its own employee.Documented: the exactly-one-back-reference rule (none = unrelated rows, several = ambiguous, both parse-time errors rather than a silently wrong recipient list), and the fail-soft-per-row contract - a fan-out never fails its activity, because retrying would resend to every recipient already served and a partial fan-out cannot be made idempotent.
🤖 Generated with Claude Code