Skip to content

rename {resource}_id guidance to id #111

Description

@toumorokoshi

inspired by: aip-dev/google.aip.dev#1063

For google, the convention of {resource}_id is well ingrained into the sdks, and changing that expectation would be harmful for customers and the generated clients.

For overall APIs, removing the need to unnescessary inclusions of the resource singular would reduce the cost of code generated tooling.

We should look at changing the guidance in the general AIPs. @rofrankel also has a doc that suggests that we may want to re-evaluate the naming scheme on a broader level (e.g. with the convention to have name).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions