Read 38 ~ Asynchronous Actions
By Abdallah obaid
NAME | URL |
---|---|
Home | Home. |
Prep | Prep: Engineering Topics. |
Read 01 | Node Ecosystem, TDD, CI/CD. |
Read 02 | Classes, Inheritance, Functional. |
Read 03 | Data Modeling & NoSQL Databases. |
Read 04 | Advanced Mongo/Mongoose. |
Read 05 | Linked Lists. |
Read 06 | HTTP and REST. |
Read 07 | Express. |
Read 08 | Express Routing & Connected API. |
Read 09 | API Server. |
Read 10 | Stacks and Queues. |
Read 11 | Authentication. |
Read 12 | OAuth. |
Read 13 | Bearer Authorization. |
Read 14 | Access Control (ACL). |
Read 15 | Trees. |
Read 16 | Event Driven Applications. |
Read 17 | TCP Servers. |
Read 18 | Socket.io. |
Read 19 | Message Queues. |
Read 26 | Component Based UI. |
Read 27 | React Testing and Deployment. |
Read 28 | Props and State. |
Read 29 | Component Composition. |
Read 30 | Hash Tables. |
Read 31 | Hooks API. |
Read 32 | Custom Hooks. |
Read 33 | Context API. |
Read 34 | <Login /> and <Auth /> . |
Read 35 | Graphs. |
Read 36 | Application State with Redux. |
Read 37 | Combined Reducers. |
Read 38 | Asynchronous Actions. |
# Asynchronous Actions ———————————- ## Thunking for Data:
- Thunkis middleware allows you to write action creators that return a function instead of an action. The thunk can be used to delay the dispatch of an action, or to dispatch only if a certain condition is met.
- Using Redux actions to connect to remote APIs via Thunk Middleware.
- Thunk will inspects every dispatched action and then either lets it go through (in the case of a normal action that returns an object) or it processes the function and then dispatches what that function returns.
- In Redux, middleware is implemented as a curried function that ultimately evaluates the action and determines whether it’s a function or not. If so, it gets invoked with the store’s dispatch() and getState() methods. Otherwise (a normal action creator), it simply runs your action.
- Thunk provides more stability and error checking for us.