Skip to content

Commit

Permalink
address comments
Browse files Browse the repository at this point in the history
  • Loading branch information
ymqytw committed May 10, 2017
1 parent 4766413 commit 84c680b
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion contributors/design-proposals/multi-fields-merge-key.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,10 @@ If a merge key has multiple fields, it will be a string of merge key fields sepe
If a merge key only has one field, it will be the same as before, i.e. `patchMergeKey:"<key1>"`.

There are no patch format changes.
Additional fields are just extra fields in the patch.
Patches for fields that have multiple fields in the merge key must include all of the fields of the merge key in the patch.

If a new API uses multi-fields merge key, all the fields of the merge key are required to present.
Otherwise, the server will reject the patch.

E.g.
foo and bar are the merge keys.
Expand Down

0 comments on commit 84c680b

Please sign in to comment.