-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Broken server side subscription on Meteor 2.0 #154
Comments
@StorytellerCZ Have you encounter anything like this? |
@jankapunkt is probably the better person to ask. |
Thanks, @StorytellerCZ. |
Hi @aessig @StorytellerCZ , I currently develop autocomplete for AutoForm but it's generic and not bound to this package (but can be used with this package). I actually am not very deep into this package so I can't really help (I also have always big trouble understanding cofeescript...). @aessig do you use some package or technique to cache subscriptions like kadira SubsManager or ccorcos SubsCache? |
Thanks for this quick reply. No, I don't use any subs manager. If you have an alternative for AutoForm, it might be a solution too. Is it based also on pub/sub or methods? Do you have anything public? |
Regarding AutoForm: this is simply the ui and form component (the input field + some rendering) but you have to provide the autocomplete options on your own (so it is compatible with any implementation) so I think this won't be an alternative. You can check the latest PR on it. |
Thanks @jankapunkt. I will have a look. |
What
The client collection gets fed with results and the results accumulate. So we have 5 entries (for example) at the first letter input, then when the second letter is typed in, we have 10 entries in the client collection. The client-side of the code displays everything it has in the collection, therefore the autocomplete doesn't work. It looks like the _publishCursor doesn't purge the collection every time it's updated.
Reproduction
Here is what the code looks like on the server:
The text was updated successfully, but these errors were encountered: