You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`--from-file` updates only fields that the People API allows via `people.updateContact``updatePersonFields`.
34
+
35
+
Practical rule: include only fields you want to change, at the top level of the JSON object (for example `urls`, `biographies`, `names`, `emailAddresses`, `phoneNumbers`, `addresses`, `organizations`, ...).
36
+
37
+
If the JSON contains unsupported fields (for `updateContact`), gog errors instead of silently ignoring them.
38
+
39
+
Notes:
40
+
41
+
- Some fields are “singleton” for contact sources. Don’t include more than one value for `biographies`, `birthdays`, `genders`, or `names`.
42
+
- If you update `memberships`, the Person must include contact group memberships or the API will error.
43
+
44
+
## Clearing Fields
45
+
46
+
Clearing list fields is supported by including the key with an empty value:
47
+
48
+
- Use `[]` to clear a list field (example: `"urls": []`)
49
+
- Use `null` to clear a list field (example: `"biographies": null`)
50
+
51
+
## Concurrency (ETags)
52
+
53
+
To avoid overwriting concurrent contact edits, gog compares the JSON etag with the current contact etag:
54
+
55
+
- If they mismatch, update fails with an etag error.
56
+
- Use `--ignore-etag` to apply your JSON changes to the latest version anyway.
0 commit comments