Please enable JavaScript.

Coggle requires JavaScript to display documents.

Redux Saga (Intro (Helps manage application side effects (side effects can…

- - - - asynchronous things like data fetching
      - impure things like accessing browser cache
      - [thought]
        does side effects mean the outcome of the task depends on the state of an external system
  - - - Spanwed by a redux action
      - it has access to the entire redux state
      - and it can dispatch actions
      - it helps compose several side effects
        
        commonly sequentially using yield
        
        but one can also use common control flow structures like if, while, for
- - - - declarative way to inform middleware what action needs to be dispatched
    - - a declarative way to inform the description of the task to the middleware
      - the saga itself does not invoke the task
        
        the middleware carries out that responsibility
        
        because saga only describe the task
        
        it is very easy to test the saga
        
        otherwise we would have required mock functions
        
        which might be brittle
      - we can also invoke methods on objects using call
- - - - like spawn a new network request at every click of a button