Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upProtobuf.JS 6.45; SyncRecord as JS object #28
Merged
Conversation
|
oops, good catch. i changed RECEIVE_SYNC_RECORDS to GET_EXISTING_OBJECTS in brave/browser-laptop@b9467cc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
ayumi commentedJan 8, 2017
•
edited
Fix #6
Ensures SyncRecord IPC message compatibility.
Upgrades protobuf.js to 6.4.5 and converts api.proto to static JS code.
SyncRecord.lookup('Site'). This is minor beause you'd just doSyncRecord.Site.oneofattributes have issues, notably SyncRecord .objectData is stuck as "bookmark". As a workaround I made a helper: serializer.getSyncRecordObjectData()Test plan for (1):
yarn distto browser-laptop#feature/syncingconsole.log(records).sending recordwith the GET_EXISTING_OBJECTS record. They should be the same.