Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sync API consistent: always (before, after) #1303

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

rmunn
Copy link
Contributor

@rmunn rmunn commented Dec 4, 2024

Also update all call sites so that code behavior remains the same.

Fixes #1293.

This is #1301 rebased on top of #1267 now that #1267 is the only open PR that touches the update API.

@rmunn rmunn requested a review from hahn-kev December 4, 2024 05:26
@rmunn rmunn self-assigned this Dec 4, 2024
Base automatically changed from feat/new-update-api-senses to develop December 6, 2024 02:27
@rmunn rmunn force-pushed the chore/consistent-sync-api-before-after branch from 613a1cd to f30a2db Compare December 6, 2024 02:30
@hahn-kev hahn-kev assigned hahn-kev and unassigned rmunn Dec 9, 2024
@myieye myieye assigned myieye and unassigned hahn-kev Dec 11, 2024
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.

Use consistent parameter order of (before, after) throughout update APIs
3 participants