mirror of
https://github.com/protocolbuffers/protobuf
synced 2026-08-26 02:23:14 -04:00
Auto-generate files after cl/859195047
This commit is contained in:
parent
6ebdf851ba
commit
f3dc7b4b41
4 changed files with 42 additions and 48 deletions
Binary file not shown.
|
|
@ -151,24 +151,22 @@ namespace Google.Protobuf.WellKnownTypes {
|
|||
/// An implementation may provide options to override this default behavior for
|
||||
/// repeated and message fields.
|
||||
///
|
||||
/// In order to reset a field's value to the default, the field must
|
||||
/// be in the mask and set to the default value in the provided resource.
|
||||
/// Hence, in order to reset all fields of a resource, provide a default
|
||||
/// instance of the resource and set all fields in the mask, or do
|
||||
/// not provide a mask as described below.
|
||||
/// Note that libraries which implement FieldMask resolution have various
|
||||
/// different behaviors in the face of empty masks or the special "*" mask.
|
||||
/// When implementing a service you should confirm these cases have the
|
||||
/// appropriate behavior in the underlying FieldMask library that you desire,
|
||||
/// and you may need to special case those cases in your application code if
|
||||
/// the underlying field mask library behavior differs from your intended
|
||||
/// service semantics.
|
||||
///
|
||||
/// If a field mask is not present on update, the operation applies to
|
||||
/// all fields (as if a field mask of all fields has been specified).
|
||||
/// Note that in the presence of schema evolution, this may mean that
|
||||
/// fields the client does not know and has therefore not filled into
|
||||
/// the request will be reset to their default. If this is unwanted
|
||||
/// behavior, a specific service may require a client to always specify
|
||||
/// a field mask, producing an error if not.
|
||||
/// Update methods implementing https://google.aip.dev/134
|
||||
/// - MUST support the special value * meaning "full replace"
|
||||
/// - MUST treat an omitted field mask as "replace fields which are present".
|
||||
///
|
||||
/// As with get operations, the location of the resource which
|
||||
/// describes the updated values in the request message depends on the
|
||||
/// operation kind. In any case, the effect of the field mask is
|
||||
/// required to be honored by the API.
|
||||
/// Other methods implementing https://google.aip.dev/157
|
||||
/// - SHOULD support the special value "*" to mean "get all".
|
||||
/// - MUST treat an omitted field mask to mean "get all", unless otherwise
|
||||
/// documented.
|
||||
///
|
||||
/// ## Considerations for HTTP REST
|
||||
///
|
||||
|
|
|
|||
|
|
@ -157,24 +157,22 @@ typedef GPB_ENUM(GPBFieldMask_FieldNumber) {
|
|||
* An implementation may provide options to override this default behavior for
|
||||
* repeated and message fields.
|
||||
*
|
||||
* In order to reset a field's value to the default, the field must
|
||||
* be in the mask and set to the default value in the provided resource.
|
||||
* Hence, in order to reset all fields of a resource, provide a default
|
||||
* instance of the resource and set all fields in the mask, or do
|
||||
* not provide a mask as described below.
|
||||
* Note that libraries which implement FieldMask resolution have various
|
||||
* different behaviors in the face of empty masks or the special "*" mask.
|
||||
* When implementing a service you should confirm these cases have the
|
||||
* appropriate behavior in the underlying FieldMask library that you desire,
|
||||
* and you may need to special case those cases in your application code if
|
||||
* the underlying field mask library behavior differs from your intended
|
||||
* service semantics.
|
||||
*
|
||||
* If a field mask is not present on update, the operation applies to
|
||||
* all fields (as if a field mask of all fields has been specified).
|
||||
* Note that in the presence of schema evolution, this may mean that
|
||||
* fields the client does not know and has therefore not filled into
|
||||
* the request will be reset to their default. If this is unwanted
|
||||
* behavior, a specific service may require a client to always specify
|
||||
* a field mask, producing an error if not.
|
||||
* Update methods implementing https://google.aip.dev/134
|
||||
* - MUST support the special value * meaning "full replace"
|
||||
* - MUST treat an omitted field mask as "replace fields which are present".
|
||||
*
|
||||
* As with get operations, the location of the resource which
|
||||
* describes the updated values in the request message depends on the
|
||||
* operation kind. In any case, the effect of the field mask is
|
||||
* required to be honored by the API.
|
||||
* Other methods implementing https://google.aip.dev/157
|
||||
* - SHOULD support the special value "*" to mean "get all".
|
||||
* - MUST treat an omitted field mask to mean "get all", unless otherwise
|
||||
* documented.
|
||||
*
|
||||
* ## Considerations for HTTP REST
|
||||
*
|
||||
|
|
|
|||
|
|
@ -96,22 +96,20 @@ use Google\Protobuf\RepeatedField;
|
|||
* }
|
||||
* An implementation may provide options to override this default behavior for
|
||||
* repeated and message fields.
|
||||
* In order to reset a field's value to the default, the field must
|
||||
* be in the mask and set to the default value in the provided resource.
|
||||
* Hence, in order to reset all fields of a resource, provide a default
|
||||
* instance of the resource and set all fields in the mask, or do
|
||||
* not provide a mask as described below.
|
||||
* If a field mask is not present on update, the operation applies to
|
||||
* all fields (as if a field mask of all fields has been specified).
|
||||
* Note that in the presence of schema evolution, this may mean that
|
||||
* fields the client does not know and has therefore not filled into
|
||||
* the request will be reset to their default. If this is unwanted
|
||||
* behavior, a specific service may require a client to always specify
|
||||
* a field mask, producing an error if not.
|
||||
* As with get operations, the location of the resource which
|
||||
* describes the updated values in the request message depends on the
|
||||
* operation kind. In any case, the effect of the field mask is
|
||||
* required to be honored by the API.
|
||||
* Note that libraries which implement FieldMask resolution have various
|
||||
* different behaviors in the face of empty masks or the special "*" mask.
|
||||
* When implementing a service you should confirm these cases have the
|
||||
* appropriate behavior in the underlying FieldMask library that you desire,
|
||||
* and you may need to special case those cases in your application code if
|
||||
* the underlying field mask library behavior differs from your intended
|
||||
* service semantics.
|
||||
* Update methods implementing https://google.aip.dev/134
|
||||
* - MUST support the special value * meaning "full replace"
|
||||
* - MUST treat an omitted field mask as "replace fields which are present".
|
||||
* Other methods implementing https://google.aip.dev/157
|
||||
* - SHOULD support the special value "*" to mean "get all".
|
||||
* - MUST treat an omitted field mask to mean "get all", unless otherwise
|
||||
* documented.
|
||||
* ## Considerations for HTTP REST
|
||||
* The HTTP kind of an update operation which uses a field mask must
|
||||
* be set to PATCH instead of PUT in order to satisfy HTTP semantics
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue