docs(intent): a re-parented child repairs both parents - #205
Merged
Conversation
Roll-ups now generate a fourth handler on the child's -rekeyed topic, so the parent a child was moved AWAY from is corrected with the one that received it instead of waiting for an unrelated change. And the -rekeyed publish is no longer tied to the form submit: a targeted write (a process step's setRelationField, a resolves: lookup, a task form) publishes both the previous and the written row, which is the only signal either side gets on that path.
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.
Documents the fix for dirigible#6819 on
/help/intent/glue:RollupOnRekey, binds the child's-rekeyedtopic, so the parent a child was moved AWAY from is corrected together with the one that received it, instead of waiting for an unrelated child of that parent to change.-rekeyedpublish is no longer tied to the form submit. A targeted write — a process step'ssetRelationField, aresolves:lookup, a task form persisting what it edited — moves the same column and deliberately raises no-updated, so it publishes the previous AND the written row on-rekeyed: the only topic the roll-up / aggregate handlers subscribe to, which repairs both sides without re-firing every reaction bound to the record.Vendor-neutral counterparts: intent-specification#43, intentfile.github.io#34.