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).
Our
XxxInfoclasses have two fields with a similar namexxxId: this fields is of typeXxxIdand holds a user-defined identity for the resourceid: this fields holds a service-generated (opaque) idWe should provide a better naming to easily distinguish the two fields. Possible solutions are:
idtogeneratedId(this is the preferred way so far)idtoopaqueIdNote: this issue also applies to other classes (e.g. compute's
DiskImageConfiguration).