-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the reasoning for a Request FSA with error flag? (vs a Failure FSA) #44
Comments
@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. |
Pinging #26, since it is relevant to this issue. |
I am also confused. When I get an API request error like this :
The |
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 |
@aris-b a @danludwig Have you looked into using the |
Previously: RSAA -> Request FSA -> Request Error FSA Now: RSAA -> Request FSA -> Failure FSA Closes agraboso#26 agraboso#44 agraboso#99
Fixed in #175 |
As i understand now - when a
REQUEST
FSA gets fired, this can result in a:REQUEST
FSA with error flag (for example when the API request cant be made)SUCCESS
FSA (for example for API response 200 OK)FAILURE
FSA (for example for API response 404 Not Found)But in my view one
REQUEST
FSA should result in (only and) exactly one FSA, eitherSUCCESS
orFAILURE
.I haven't actually used it, but i dont really understand the first one. Whats the argument for not returning a
FAILURE
FSA in that case?The text was updated successfully, but these errors were encountered: