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

fix(AIP-134): add full replace usage caveats #1453

Merged
merged 6 commits into from
Jan 14, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions aip/general/0134.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,11 @@ message UpdateBookRequest {
populated (have a non-empty value).
- Update masks **must** support a special value `*`, meaning full replacement
(the equivalent of `PUT`).
- API producers need to be concious of how adding new, mutable fields to a
noahdietz marked this conversation as resolved.
Show resolved Hide resolved
resource will be handled when consumers use `*` without knowledge of said
new, mutable fields. Likewise consumers need to be concious of using `*`
noahdietz marked this conversation as resolved.
Show resolved Hide resolved
only when the risks of doing so are acceptable. In general, it is safest
to explicitly specify the fields to update rather than use `*`.
- The request message **must not** contain any other required fields, and
**should not** contain other optional fields except those described in this
or another AIP.
Expand Down