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

It is necessary to refactor the MyTimline and GlobalTimeline data binding #22

Open
GSoster opened this issue May 25, 2016 · 2 comments
Open
Assignees

Comments

@GSoster
Copy link
Owner

GSoster commented May 25, 2016

It is obvious that the way it work now is not good practice and was done just to make it work.
It is necessary to make the helpers manage where from the data will be fetched based on the Session. That way it will be possible to remove some html/js files and make the whole process more maintainable.

@GSoster GSoster self-assigned this May 25, 2016
@GSoster
Copy link
Owner Author

GSoster commented May 25, 2016

Part of this Issue was already solved in this commit:
b090367
It made possible to remove two files (globaltimeline.js and globaltimeline.html) since now only one template is necessary and the source of the data is provided by the router.

@GSoster
Copy link
Owner Author

GSoster commented Aug 18, 2016

Lots of changes were made in the commits:
71553b4
27ce7dd
1daf937
Now there is no autopublish package anymore. Informations from collections are passed to the client through Subscriptions.
It still necessary to solve a few problems due to Meteor.userId not being acceptable inside publish methods.

Infos about how multiple subscriptions for the same collections work can be found here:
https://stackoverflow.com/questions/19826804/understanding-meteor-publish-subscribe/21853298#21853298

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

No branches or pull requests

1 participant