kevinl (36) [Avatar] Offline
It seems more than appropriate to also cover redux-observable. It leverages ESNext observables with is significantly a better async abstraction than promises (inc. async/await) and callback-based systems.

It's also very popular to be used within React apps and redux will often also be used with libraries or frameworks that already leverage observables with significant gains over existing async abstractions such as RxJS & Angular 2 (which uses RxJS to provide observables be continuously available).

Accordingly, it made sense to mention this as a suggestion.
Frances L. (7) [Avatar] Offline
Thanks so much! I'm the development editor for this video, but I will get Thomas in here to see your note!
Thomas Tuts (1) [Avatar] Offline
Hi Kevin,

Thanks so much for your suggestion! In this course we opted to use redux-thunk for async actions since they're just functions. This means they're far easier to grok than observables or sagas, which are concepts that most JS developers aren't familiar with yet.

I do agree with the sentiment that it should be covered, I'm just not sure if this introductory course is the right place for that. Maybe this is something that could be covered in a more advanced Redux course, though!
Mia (1) [Avatar] Offline
These kinds of epics come up a lot while working with 3rd party reducer libraries like redux-form and react-router-redux, so a good strategy for them is vital!