Closed jskeet closed 4 months ago
Consider the following proto:
message Abc { string location = 1 [ (google.api.resource_reference) = { type: "locations.googleapis.com/Location" } ]; message Def { string location = 1 [ (google.api.resource_reference) = { type: "locations.googleapis.com/Location" } ]; } }
Currently we'll generate a LocationAsLocationName property for Abc, but not for Def (it's in ResourceNamesGenerator.ProtoMessagePartials).
LocationAsLocationName
Abc
Def
Generating the extra properties is:
... on the other hand, this inconsistency is annoying.
I don't think we've had a single customer request this.
The following fields would have resource annotations generated for them:
Will close here, reopen internally as P3.
Consider the following proto:
Currently we'll generate a
LocationAsLocationName
property forAbc
, but not forDef
(it's in ResourceNamesGenerator.ProtoMessagePartials).Generating the extra properties is:
... on the other hand, this inconsistency is annoying.
I don't think we've had a single customer request this.
The following fields would have resource annotations generated for them: