What is the reasoning for a Request FSA with error flag? (vs a Failure FSA) about redux-api-middleware HOT 6 CLOSED

I am also confused. When I get an API request error like this :

{ 
 [RequestError: request to https://xxxxx failed, reason: self signed certificate]
 name: 'RequestError',
 message: 'request to https://xxxx failed, reason: self signed certificate' },
 meta: undefined,
 error: true }

The FAILURE FSA is not triggered. I see this error by logging on REQUEST FSA.
So my question is, when actually FAILURE FSA gets triggered ?

from redux-api-middleware.

@barrystaes This is an issue that I struggled with — see this comment of mine. The solution that I came up with might not be to everyone's taste nor even the most logical one. I think a thorough discussion is in order before we push out a v2.

from redux-api-middleware.

Pinging #26, since it is relevant to this issue.

from redux-api-middleware.

Found this when searching for how to customize the action payload when a REQUEST FSA is dispatched with an error flag. Seems you can't? For example, if I attach a key property to the initial REQUEST payload, there is no way to correlate that key's value back to the request that failed?

from redux-api-middleware.

So my question is, when actually FAILURE FSA gets triggered ?

@aris-b a FAILURE FSA is triggered when the response is not 200 OK, and if the response was 200 OK expect a SUCCESS FSA.
If the request could not be made at all, expect a REQUEST FSA with error:true. This behavior is documented at lifecycle in readme.md and its also outlined in the first post of this issue..

@danludwig Have you looked into using the meta property, which is there for the purpose of adding metadata to use later.

from redux-api-middleware.

Fixed in #175

from redux-api-middleware.