Undefined behavior when using the if and unless predicates

Open
#28 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby

Research direction

Start at the TableSync.sync entry point and trace how the if and unless predicates are applied to update and destroy events. Done means both types of updates honor the configured predicate consistently.

Written by the indexing model from the issue text.

Description

Now:
If I setup synchronization with if predicate like
TableSync.sync(self, if: -> (*) { syncable? })
model will send updates if predicate is truthy, but destroy will always send.

What I want:
The model must check predicates when sending both types of updates.

Dominant language
Ruby
Stars
27
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from umbrellio/table_sync

All issues in umbrellio/table_sync

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.