-
Notifications
You must be signed in to change notification settings - Fork 64
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
sync-collection for client #37
Conversation
done @emersion :D |
ouch, for some reason the PR got mixed up with #36 which you already merged.... just ignore that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update, this version looks much better. I left a few more comments.
Can you rebase against the latest commit from master and squash all commits into a single one? See https://git-rebase.io/
1b6a9fe
to
6686a53
Compare
done. |
d594034
to
7af66c2
Compare
bc51215
to
8710713
Compare
fixed |
267bad1
to
f5c8b6a
Compare
@emersion I've implemented all of your comments... can you please re-review it? |
f5c8b6a
to
7da1bd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update! Here's a last round of comments, apart from that this LGTM and is ready for merging.
@emersion any comment? |
7da1bd6
to
e57f9a4
Compare
done. @emersion Let's merge 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Basic sync-collection operation for client
partial implementation of #35