Negative `pending` when using `sendRequest`

When using the low-level API with sendRequest the pending state becomes negative e.g:

// saga
function* loadSomething(): Saga {
  const {response, error} = yield call(sendRequest, actions.fetchSomething());
}
// reducer
....
    something: requestsReducer({
      actionType: FETCH_SOMETHING,
      getData: (state, action) => action.data,
    }),
...

[burgalon]

(by saying “same action”) I mean that fetchBooks() can be called in the same app in two different scenarios:

1. From saga function *watchBookUpdate() {yield put.resolve(fetchBooks)}}
2. From <BookList> function componentDidMount {this.props.fetchBooks();}

[klis87]

@mihaisavezi I am glad you solved it, anyway sendRequest for sure will be gone from this library, as it won’t be powered by sagas anymore, just pure redux

I recommend you doing the following:

1. pass promisify: true to handleRequests and add requestsMiddleware to middlewares like in docs
2. if u have an action like:

const fetchSth = () => ({
  type: 'FETCH_STH',
  request: { url: '/' },
  meta: { asPromise: true },
})

1. you can dispatch it anywhere like store.dispatch(fetchSth()).then().catch()
2. or you can do the same with saga, like const response = yield putResolve(fetchSth()), or with older version of saga const response = yield put.resolve(fetchSth())
3. you can pass autoPromisify: true to handleRequests to promisify all actions, so meta.asPromise is not necessary anymore

Probably in the future version promisifying will be turned on always, so promisify, autoPromisify and meta.asPromise will be removed too