You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Should we rename "identity" as "reference" in javadoc? #735
In services that have model objects with "id" as a field, we try to differentiate between that "id" field and the "identity" of that object (the information necessary to reconstruct/access that object via the service). For example, blobs have "id" fields, but gcloud-java-storage also has a BlobId class that contains the bucket name, blob name, and generation.
In the javadoc, we use "identity" to describe classes like BlobId. I feel that "reference" is a slightly better word than "identity" because "reference" is a more commonly used word and thus would make the javadoc read more nicely. Also, "id" is a shorthand for "identity" (and a user could potentially assume they're related), whereas "reference" might differentiate the two items more clearly.
-1 for this rename. I have seen "identity" referring to a rather complex compounded object descriptor which is exactly what we are doing in this case. Thus, it seems natural. I would be struggling with understanding the meaning of a "reference".
Activity
mziccard commentedon Mar 10, 2016
I agree that reference is more commonly used but also has a different meaning in the context of programming.
mderka commentedon Mar 11, 2016
-1 for this rename. I have seen "identity" referring to a rather complex compounded object descriptor which is exactly what we are doing in this case. Thus, it seems natural. I would be struggling with understanding the meaning of a "reference".
ajkannan commentedon Mar 12, 2016
Alright, closing this as it seems like identity is more popular.
chore(main): release 2.2.1 (#735)
chore: update java template (googleapis#1367) (googleapis#735)
chore(deps): update dependency com.google.cloud:google-cloud-tasks to…
chore(main): release 2.2.3 (#735)
build(deps): update dependency org.apache.maven.plugins:maven-javadoc…
chore(bazel): Update WORKSPACE files for rules_gapic, gax_java, gener…
chore(main): release 2.4.5 (#734)
chore(main): release 2.4.4 (#740)
5 remaining items
chore(main): release 3.0.0 (#740)
chore(deps): update dependency com.google.cloud:google-cloud-logging …
chore(deps): update dependency com.google.cloud:google-cloud-logging-…
chore(deps): update dependency com.google.cloud:libraries-bom to v25.…
chore: update java docfx doclet (#735)
chore(deps): update dependency com.google.cloud:google-cloud-logging …
chore: update java docfx doclet (#735)
build(deps): update dependency org.apache.maven.plugins:maven-project…
deps: update dependency com.google.cloud:google-cloud-storage to v2.1…
chore: release 0.123.15 (#736)
deps: update dependency com.google.cloud:google-cloud-storage to v2.1…
chore: release 0.123.15 (#736)
chore: remove distributionManagement section (#735)
chore: remove distributionManagement section (#735)
chore: regenerate README (googleapis#735)