$collection.bind publisher parameter (string) being ignored? about angular-meteor HOT 7 CLOSED

The work around that I'm using is to use the selector parameter of the $collection initializer, as documented at http://angularjs.meteor.com/api/collection. I pass the exact parameters to that as I am to the publisher, and the subset is returned as expected.

I don't know if there are performance implications by doing it this way, as I haven't examined the code to see where the request is run, but at least it's a work around.

from angular-meteor.

Looks like the work around isn't so great. Trying to update a collection bound in this way just leads to the document being deleted rather than updated.

from angular-meteor.

@sheppe I've just tested the subscribe parameter and it works..

Can you add a MeteorPad and maybe I can help more?

Maybe you are subscribing in another place to the same collection?
Remember, Meteor aggregates all the information from the collection that got to the client at any point in time so all the information might be coming from another subscription in your code.

Another thing is to check is you removed the autopublish package..

from angular-meteor.

It's a little too complex for a meteor pad, but clearly I'm doing something wrong.

I only reference the publishers in one controller, but there are three different publishers referencing a single collection in that controller. Each publisher returns a different subset of results, but all of them together would end up returning everything as I have been experiencing.

Is it possible an interaction between the three publishers on a single collection is causing this? I did reduce the number of binds in the controller to use just one publisher, and it still returned all documents.

I do reference the base collection/all documents in a different view and controller. Are you saying that the publishers will not return a properly filtered set of results doing it that way? I'm fairly new to Meteor, so perhaps I've made a rookie mistake here.

Lastly, I do have autopublish removed. :)

Thanks!

from angular-meteor.

@sheppe exactly, the publish/subscribe mechanism is not for filtering, filtering is does on the collection (or inside the publish Method).
We are working now on adding filtering + sorting + pagination to the tutorial using this library:
https://github.com/matteodem/meteor-easy-search

Reading that library might help you better understand how it works

from angular-meteor.

@Urigo Okay, thanks.

For now I've just implemented custom Angular filters to display the subsets of data, and to keep the data manageable I'm using the pagination feature of $collection.bind.

Thanks for taking on this project, by the way. Angular and Meteor are two of my favourite frameworks, and combining them is brilliant!

from angular-meteor.

Great.
I've added a note in the documentation of $collection.bind about the subscribe parameters thanks to your issue

from angular-meteor.