Delete methods: Method signature

This rule enforces that all Delete standard methods have a google.api.method_signature annotation with a value of "name", as mandated in AIP-135.

Details

This rule looks at any method beginning with Delete, and complains if the google.api.method_signature annotation is missing, or if it is set to any value other than "name". Additional method signatures, if present, are ignored.

Examples

Incorrect code for this rule:

// Incorrect.
rpc DeleteBook(DeleteBookRequest) returns (google.protobuf.Empty) {
  // A google.api.method_signature annotation should be present.
}

// Incorrect.
rpc DeleteBook(DeleteBookRequest) returns (google.protobuf.Empty) {
  option (google.api.method_signature) = "book";  // Should be "name".
}

Correct code for this rule:

// Correct.
rpc DeleteBook(DeleteBookRequest) returns (google.protobuf.Empty) {
  option (google.api.method_signature) = "name";
}

Disabling

If you need to violate this rule, use a leading comment above the method. Remember to also include an aip.dev/not-precedent comment explaining why.

// (-- api-linter: core::0135::method-signature=disabled
//     aip.dev/not-precedent: We need to do this because reasons. --)
rpc DeleteBook(DeleteBookRequest) returns (google.protobuf.Empty) {
  option (google.api.method_signature) = "book";
}

If you need to violate this rule for an entire file, place the comment at the top of the file.