This repository has been archived by the owner on Jul 31, 2020. It is now read-only.
Releases: brave/sync
Releases · brave/sync
v1.2.2
v1.2.1
Changes:
browser -> webview FETCH_SYNC_RECORDS:
- Now calls GET_EXISTING_OBJECTS even when records is an empty set.
webview -> browser GET_EXISTING_OBJECTS:
- New param,
isTruncatedwhich notifies browsers if there are additional records.
Fixes:
FETCH_SYNC_DEVICES
- Stops returning all preferences (#75).
v1.2.0
- New Browser -> Webview IPC call:
FETCH_SYNC_DEVICES- Requests device records. Webview responds with RESOLVED_SYNC_RECORDS.
- Changed Webview -> Browser call:
GET_EXISTING_OBJECTS- List of JS records includes a new property:
syncTimestamp - syncTimestamp has been stored in the record S3 key and not proto object, and wasn't exposed previously.
- useful for determining when a record was uploaded.
- List of JS records includes a new property:
v1.1.0
browser/lib API changes:
-
FETCH_SYNC_RECORDS
- New param:
limitResponse(boolean). when set to true, limits response to 1000 (previously unbounded) - New response param (call to browser GET_EXISTING_OBJECTS):
lastRecordTimestamp(number), the timestamp in milliseconds of the last record in a response batch. Useful as a cursor for traversing batches of 1000. - ⛱ Changes should be non-breaking and compatible with existing browser Sync implementations.
- New param:
-
New message sent to browsers: SYNC_SETUP_ERROR
- might have useful info previously stuck in the sync lib
QoL (yarn build doesn't yarn upgrade .. pinned express)
v1.1.0-pre.1
Changes to IPC interface:
- GET_EXISTING_OBJECTS (sent by lib in response to FETCH_SYNC_RECORDS):
- Now includes an additional param: timestamp (in ms) of the final record
- Returns max 1000 records at once (was previously unbounded)
Notes:
- In browser-laptop, we have been calling FETCH_SYNC_RECORDS with startAt as timestamp in seconds, but moving forward we'll use milliseconds for more precise traversal of record batches.