[GH-ISSUE #6] Sync fetching fresh values for "mutations" event listeners #4

Closed
opened 2026-05-23 08:33:47 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @appy-one on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/appy-one/acebase-client/issues/6

Originally assigned to: @appy-one on GitHub.

The synchronization process fetches fresh values from the server for nodes with "mutations" event listeners on it. This should not be done. If the client needs to refresh an entire node's value after a reconnect, it has to subscribe to the "sync_done" event and get() the new value manually. (client.on("sync_done", callback))

Originally created by @appy-one on GitHub (Mar 3, 2021). Original GitHub issue: https://github.com/appy-one/acebase-client/issues/6 Originally assigned to: @appy-one on GitHub. The synchronization process fetches fresh values from the server for nodes with "mutations" event listeners on it. This should not be done. If the client needs to refresh an entire node's value after a reconnect, it has to subscribe to the ```"sync_done"``` event and ```get()``` the new value manually. (```client.on("sync_done", callback)```)
gitea-mirror added the
bug
label 2026-05-23 08:33:47 -06:00
Author
Owner

@appy-one commented on GitHub (Mar 3, 2021):

Fix published in acebase-client v1.1.1

<!-- gh-comment-id:789764504 --> @appy-one commented on GitHub (Mar 3, 2021): Fix published in acebase-client v1.1.1
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/acebase-client#4
No description provided.