Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SubsCache.ready() is unreliable #12

Open
thebarty opened this issue Aug 27, 2018 · 1 comment
Open

SubsCache.ready() is unreliable #12

thebarty opened this issue Aug 27, 2018 · 1 comment

Comments

@thebarty
Copy link

Hi guys,

just letting you know: I switched to using the original https://github.com/kadirahq/subs-manager which works much more stable for me.

Problem: globalSubscriptionManager.ready() acts unreliable and after clicking a few links in the ui returns "false"

// using Blaze Components
onCreated() {
  super.onCreated()
  // TemplateLevel autorun
  this.autorun(() => {
    globalSubscriptionManager.subscribe('sub1')
    globalSubscriptionManager.subscribe('sub2')
  })
}

There seems to be something wrong in the codebase. For me it is globalSubscriptionManager .ready() that acts totally unreliable. Actually all references to the individual subscriptions (which I get via globalSubscriptionManager.subscribe() return (ready()===true). BUT still the global globalSubscriptionManager .ready() returns false.

The bug exists in this package and also in ccorcos/meteor-subs-cache#20.

@gsovereignty
Copy link
Member

Thanks for letting us know! We'll probably switch back too then, I forgot what the original problem was but this looks pretty bad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants