Repository navigation
Datastore: Use new Key object to easily reference parts of a key path #48
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
Description
Activity
- added 7 commits that reference this issue
on Nov 8, 2016 - added a commit that references this issue
on Nov 21, 2016 - addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 6, 2020 - added a commit that references this issue
on Nov 7, 2022 - added a commit that references this issue
on Nov 8, 2022 13 remaining items
- added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 17, 2022 - added 2 commits that reference this issue
on Nov 18, 2022 - added a commit that references this issue
on Nov 18, 2022 - added a commit that references this issue
on Jan 11, 2023
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
RE: #47 (comment)
gcloud-node has made some improvements around Key objects, making it easier to reference a name/id, kind, parent, etc. We should use them here to avoid the less-readable
key.path.pop()andkey.path[n]technique.