Releases: klis87/redux-requests
redux-saga-requests v0.23.0
Added getDefaultData
to requestsReducer
config. Use instead of multiple
, if you want your initial data to be something else than null
or []
, for instance () => ({ value: null })
, set as multiple => (multiple ? [] : null)
by default, so this is backward compatible change.
Thanks to @megawac for the idea and PR!
redux-saga-requests-react v0.1.0
First release of new React bindings to redux-saga-requests
. See https://github.com/klis87/redux-saga-requests/tree/master/packages/redux-saga-requests-react for more info.
redux-saga-requests v0.22.0
Small changes which allowed adding GraphQL driver:
- by default GraphQL queries are run as
takeLatest
(like REST GET), mutations astakeEvery
(like REST POST PUT DELETE etc.) - actions with
request.query
are recognized as request actions
redux-saga-requests-mock v0.1.5
Updated Typescript types
redux-saga-requests-graphql v0.1.0
A new driver which allows to use redux-saga-requests
with GraphQL! See docs and example for more info. It requires redux-saga-requests
at least 0.22.0
version.
redux-saga-requests-fetch v0.9.6
Updated Typescript types.
redux-saga-requests-axios v0.7.6
Updated Typescript types.
redux-saga-requests v0.21.0
- added optimistic updates, so you can update your
data
in reducers before you get server response, see the bottom of https://github.com/klis87/redux-saga-requests#reducers-arrow_up - added requests cache, see https://github.com/klis87/redux-saga-requests#cache-middleware-arrow_up
- internal: refactored all tests to
jest
, which simplified configuration, allowed to get rid of too many dev dependencies (mocha, chai, sinon, nyc
)
redux-saga-requests v0.20.0
Added support to redux-saga
1.0.0-beta version. Note, that this is a backward compatible change, it still supports 0.16
version!
redux-saga-requests v0.19.0
- allowed explicit
meta.asPromise: false
to overwriterequestsPromiseMiddleware
withauto
for a given action, thanks to @nemosupremo for the idea and PR! - added action
meta.runByWatcher
flag, which can be used to disable handling it bywatchRequests
, which is by the way used by default forsendRequest
withdispatchRequestAction: true
to avoid duplicated requests when you use bothwatchRequests
andsendRequest
- removed per action config in
watchRequests
, so if you need to override globalabortOn
andtakeLatest
for an action, you can usemeta
, for example:
const fetchBooks = () => ({
type: FETCH_BOOKS,
request: {
url: '/books',
},
meta: {
takeLatest: false,
abortOn: 'LOGOUT',
},
});
- improved default
runOn...
options ofsendRequests
, so for most cases you don't even need to worry about them, see more details in readme