Skip to content
This repository has been archived by the owner on Jan 22, 2018. It is now read-only.

More explanation about middleware and handling meteor reactive data to store #12

Open
DaxChen opened this issue Dec 27, 2015 · 3 comments

Comments

@DaxChen
Copy link

DaxChen commented Dec 27, 2015

Hi,

This is the best tutorial I found for using redux with meteor, great thanks!

However, I notice that you changed a lot of code since this blog post,
and I can't quite understand how those middleware work...

I've been struggling for days to get meteor to work with redux properly, but still no luck.

Could you explain more on how you handle meteor data pub/sub and store them into redux store with those middleware?

Great Thanks!!
Dax

@genyded
Copy link

genyded commented Jan 18, 2016

+1 for example... in meals, on line 11, where do the values for userId and Date come from? Also the comments in the subscription middleware show a slightly different signature to call the middleware then what the actual calls in the app use. Better docs or comments would really help those of us new to gluing all these pieces together (outside looking in).

@djhi
Copy link
Owner

djhi commented Jan 18, 2016

Sorry guys, I don't have much time these days for this project. I'm waiting for meteor 1.3 anyway and will rewrite a lot of it when it's out. Please be patients :)

@genyded
Copy link

genyded commented Jan 18, 2016

Same here... I am under the gun for a client project though and was really hoping to use this middleware because out of everything out there this seems like the right way to go with Meteor as the 'backend'. They won't like it, but I'll have to put them off a bit longer. Thanks for spending some of you valuable spare time trying to help make things better for us all!

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

No branches or pull requests

3 participants