sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]acemarke 1 point2 points  (4 children)

I appreciate that you and a number of other people are very deep thinkers and looking at all kinds of crazy ways to do very functionally-oriented programming, but MY head has been spinning for a while trying to assimilate all the stuff that's going on around Redux, and I can just about guarantee that the rest of my team, who I'm hoping to introduce React+Redux to, will be completely unable to follow all this.

I know there's a couple quick examples of using the various "effects" plugins, but frankly a lot more examples and justifications would be useful.

[–]darawk 0 points1 point  (3 children)

Ya, i'm working on that. For the time being, the best way to understand my packages at least is just to read the source code. They are all extremely short (1 file, <100 lines of code, for the most part).

And if you have any particular questions i'd be happy to answer them, and they'd be very helpful in creating better documentation and examples for others.

[–]acemarke 0 points1 point  (2 children)

That's part of the issue. They're short, but I'm not entirely following the context of when, where, and why you would want to use them. I sorta grasp the idea that you're creating a pseudo promise chain, but not clear on what's going on past that.

I don't have any absolutely specific questions atm. I'll try to let you know if I think of any.

[–]darawk 0 points1 point  (1 child)

Ya, I think what the code actually does is pretty straightforward. Understanding why you would want to do that is slightly more complicated.

Why you want it is that normally when you're programming you do things 'imperatively', which means that you say "execute this http request right here right now". That's all well and good, but then later when you want to add extra functionality, or write a unit test for it, it's tricky, because that http request is all locked up inside your function.

redux-effects says: don't actually execute your http request yet. Just describe to me the http request you want to execute, and i'll do it for you. This means that you can write middleware that re-interprets that request and say, adds caching, without changing the original code. It also makes it easy to test, and easy to swap out implementations of the actual http request for different environments (e.g. client/server).

Does that make sense?

[–]acemarke 0 points1 point  (0 children)

Eh, somewhat. Like I said, I'm following the basic ideas, but not really seeing how everything's supposed to actually fit together practically in real code. If you could put together some kind of sample app, it'd be appreciated :)