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

Add SyncRecord.siteSetting.fields #39

Merged
merged 1 commit into from Jan 18, 2017
Merged

Conversation

@ayumi
Copy link
Contributor

ayumi commented Jan 18, 2017

Currently you can't encode a siteSetting with just a single setting . For example, a SyncRecord with siteSetting: {shieldsUp: true} encoded and decoded returns additionally all the siteSetting fields's defaults. This is because proto3 doesn't distinguish between fields set to default values and unset fields.

This PR adds the SyncRecord.siteSetting.fields with which we'll specify the changed fields. This is similar to google.protobuf.Fieldmask.

recordUtil.syncRecordAsJS() will take fields into account when converting records back to the browser client format.

@diracdeltas diracdeltas merged commit 51fcf91 into staging Jan 18, 2017
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@diracdeltas diracdeltas deleted the feature/site-setting-fields branch Jan 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.