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
Describe the problem you are trying to solve.
In the current proto specification, AIP-203 defines several google.api.field_behavior options, including required, optional, and output_only.
According to AIP-133 and AIP-134, the same object (e.g., Book book) should be used for both create and update requests, with the update_mask specifying the fields to be updated in the update interface.
Then, since the update_mask uses a string format that cannot be associated with the Book object, this makes it impossible to use update_mask to indicate specific object properties.
This inevitably leads to situations where certain properties are required fields in the create API but remain required in the update API, while not actually being updatable object properties in the update_mask.
Describe the solution you'd like
It is recommended to design new specifications for the AIP-134 documentation, such as defining a new BookUpdate object to replace the Book object. Alternatively, new behaviors like "required in update" could be defined refer to protocolbuffers/protobuf#20410
Describe the problem you are trying to solve.
In the current proto specification, AIP-203 defines several
google.api.field_behavior
options, includingrequired, optional
, andoutput_only
.According to AIP-133 and AIP-134, the same object (e.g., Book book) should be used for both create and update requests, with the update_mask specifying the fields to be updated in the update interface.
Then, since the update_mask uses a string format that cannot be associated with the Book object, this makes it impossible to use update_mask to indicate specific object properties.
This inevitably leads to situations where certain properties are required fields in the create API but remain required in the update API, while not actually being updatable object properties in the update_mask.
Describe the solution you'd like
It is recommended to design new specifications for the AIP-134 documentation, such as defining a new BookUpdate object to replace the Book object. Alternatively, new behaviors like "required in update" could be defined refer to protocolbuffers/protobuf#20410
Proto Detail
Result
The text was updated successfully, but these errors were encountered: