Standard methods: Delete
Rules for AIP-135, covering delete methods.
| Rule name | Description |
|---|---|
| force-field | Delete RPCs for resources with child collections should have a `force` field in the request. |
| http-body | Delete methods must not have an HTTP body. |
| http-method | Delete methods must use the DELETE HTTP verb. |
| http-uri-name | Delete methods must map the name field to the URI. |
| method-signature | Delete RPCs should annotate a method signature of "name". |
| request-force-field | Delete request `force` fields must have type `bool`. |
| request-message-name | Delete methods must have standardized request message names. |
| request-name-behavior | Delete RPCs should annotate the `name` field with `google.api.field_behavior`. |
| request-name-field | Delete RPCs must have a `name` field in the request. |
| request-name-reference | Delete RPCs should annotate the `name` field with `google.api.resource_reference`. |
| request-name-required | Delete RPCs must have a `name` field in the request. |
| request-required-fields | Delete RPCs must not have unexpected required fields in the request. |
| request-unknown-fields | Delete RPCs should not have unexpected fields in the request. |
| response-lro | Declarative-friendly delete methods should use long-running operations. |
| response-message-name | Delete methods must return Empty or the resource. |
Note: Because AIPs sometimes cover topics that have some overlap, some rules related to delete methods may be included in the rules for other AIPs.
View on GitHub