Skip to content

Better naming for resource identities and service ids #824

Description

@mziccard

Our XxxInfo classes have two fields with a similar name

  • xxxId: this fields is of type XxxId and holds a user-defined identity for the resource
  • id: this fields holds a service-generated (opaque) id

We should provide a better naming to easily distinguish the two fields. Possible solutions are:

  • renaming id to generatedId (this is the preferred way so far)
  • renaming id to opaqueId

Note: this issue also applies to other classes (e.g. compute's DiskImageConfiguration).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: computeIssues related to the Compute Engine API.type: cleanupAn internal cleanup or hygiene concern.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions