Batch methods: Create
Rules for AIP-233, covering batch create methods.
| Rule name | Description |
|---|---|
| http-body | Batch Create methods should use `*` as the HTTP body. |
| http-method | Batch Create methods must use the POST HTTP verb. |
| http-uri-suffix | Batch Create methods must have the correct URI suffix |
| plural-method-name | Batch Create methods must have plural names. |
| request-message-name | Batch Create methods must have standardized request message names. |
| request-parent-field | Batch Create RPCs must have a `parent` field in the request. |
| request-parent-reference | Batch Create requests should annotate the `parent` field with `google.api.resource_reference`. |
| request-requests-behavior | Batch Create requests should annotate the `requests` field with `google.api.field_behavior`. |
| request-requests-field | Batch Create RPCs should have a `requests` field in the request. |
| request-unknown-fields | Batch Create RPCs should not have unexpected fields in the request. |
| resource-reference-type | BatchCreate should use a `child_type` reference to the created resource. |
| response-message-name | Batch Create methods must have standardized response message names. |
| response-resource-field | Batch Create RPCs must have a repeated field for the resource in the response. |
Note: Because AIPs sometimes cover topics that have some overlap, some rules related to batch create methods may be included in the rules for other AIPs.
View on GitHub