Add a new sync/4 callback to include operations - #4
Merged
Conversation
michaelst
reviewed
Oct 23, 2025
michaelst
approved these changes
Oct 23, 2025
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
2 participants
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.
This introduces a new optional sync/4 callback, that receives a list or atom indicating the operation(s) being performed.
By default, sync/3 will be called, and sync/4 will only be called if it's available.
We can mix sync/3 and sync/4 in the same file, as long as the watched key is different.
When watching a list of records, operations will be a keyword list of
[operation: %Record{}], where operation is one of:insert,:updateor:delete.When watching on a single record, operation will be a single atom.