On next, dispatches requestType rather than failureType for fetch errors

[Andrew-Hagedorn-ZocDoc]

On the next branch, when there is failed request on fetch it dispatches the requestType rather than the expected failureType:

https://github.com/agraboso/redux-api-middleware/blob/next/src/middleware.js#L107

Is this the expected behavior?

[agraboso]

@Andrew-Hagedorn-ZocDoc Things are fluid right now. I hadn't touched this library in a long time and I am in the process of addressing some of the issues. In the meantime, the README might be out of date.

[Reaverart]

I'm also confused with it, how do you handle errors if it dispatches requestType?

[Reaverart]

@agraboso Sorry for nagging, but I'm trying to understand logic at this point. Why does it dispatches "request" type instead of "failure"? There is no real http request performed in case of invalid RSAA and definitely should be failure in case of error for me..
So does your request reducer checks for error true? Or.. How do you deal with errors which dispatched with request type, is there a clean way?
I've checked sample app from "Projects using redux-api-middleware" section, but there is no reducers to handle dispatched actions and no error handling..

[Reaverart]

Found a related discussion #44 and related pullreq #26

[nason]

Update: I'm hoping to push out #175 in a 3.0 release soon

[nason]

#175 was merged into the next branch (which will become the 3.0 release) and changes this behavior.

I hope to have a beta published to npm in the next few days. Closing this issue out now but feel free to re-open or continue commenting here.