Repository navigation
Add pubsub#subscription, pubsub#subscribe and pubsub#getSubscriptions #605
Description
Activity
- changed the title
[-]Add pubsub#subscription and pubsub#subscribe[/-][+]Add pubsub#subscription, pubsub#subscribe and pubsub#getSubscriptions[/+]on May 17, 2015 Can we clarify the use case on this ? #487 is long, so it'd be nice if the description said "why" we're doing this.
I have one outstanding question, which if answered, makes me OK with these new pubsub-level methods. I also would agree that if we do add these, the topic-level ones simply wrap the pubsub-level ones. That is:
Topic.prototype.subscribe = function(...) { return this.path.to.pubsubInstance.subscribe(...); };
The use case is for creating a subscription in one project that subscribes to a topic in another project.
@ryanseys SGTM. In fact, I can start working on this now, but feel free to stop me if you already had this in the works.
@stephenplusplus You can go for it!
- added a commit that references this issue
on Nov 11, 2022 7 remaining items
- added a commit that references this issue
on Jan 21, 2026 - added a commit that references this issue
on Feb 4, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 23, 2026 - added 2 commits that reference this issue
on Feb 24, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 17, 2026 - added a commit that references this issue
on Mar 18, 2026
Add
pubsub#subscriptionandpubsub#subscribeandpubsub#getSubscriptions.All the logic I feel should move to these requests and then
topic#subscriptionandtopic#subscribeandtopic#getSubscriptionsshould either be removed or rely on the pubsub version with an optionaltopicfield automatically passed in.How's this sound @stephenplusplus?
Reference: #487
/cc @tmatsuo