Konrad Lisiczyński
Konrad Lisiczyński
**Is your feature request related to a problem? Please describe.** Apologies for opening the new issue, but I am writing in regards to #2725 which is blocked now. This is...
ROADMAP
Below you can see the plan for this library, the plan starts with creating a very big release, after which API should be more stable. Then releases will be smaller...
If one doesn't want to cache anything, one won't use `meta.cache`. The only reason this option could be useful is not to include `cacheMiddleware` returned by `handleRequests` in middleware chain,...
I don't want to keep it, especially `defaultData` as it makes `getQuery` more complex than it has to be. It doesn't really do too much anyway, people can always provide...
Right now we create requests like this: ```js const fetchBook = id => ({ type: 'FETCH_BOOK', request: { url: `/books/${id}` }, meta: { requestKey: id }, }); ``` This is...
Sometimes it might be handy to refresh query data, which could allow to have more "real-time" user experience. This is how I would go about it: 1) To `RequestAction` add...
I really cannot decide, for now we use lerna independent mode, but really in the future it might be hard to know which packages are compatible with each other, for...
It could be beneficial to add something like **optimistic query**. It would allow to update `data` before query response, which could be known in advance. Use case? For example server...
Right now we do it, but I feel we shouldn't. We don't clear `data`, so I think we shouldn't `error` too. It would be cleared anyway on success, and the...
Most things in https://github.com/klis87/redux-saga-requests/tree/master/packages/redux-saga-requests/src/normalizers is implemented as recursive functions. It is surprisingly fast currently, especially with selectors, but I think it would be nice to refactor it into loops, it...