-
Notifications
You must be signed in to change notification settings - Fork 88
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
pathvars and body in store + multiple actions => weird behaviour #153
Labels
Comments
@xurei It's a correct behaviour. State hold the last request. We can add flag to save request data or skip it. What do you think about it? |
Yes I was thinking of something like that... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is related to #152, that have been merged in version 0.10.7
If several actions are bound to the same reducer (with the
reducerName
option), the pathvars and body will contain the latest action done on it. That might not be the expected behaviour.Example :
The content of
body
is kinda weird : the store still contains the results of the first call, with the update.It would make sense that the
body
stays empty.This gets even worse with a poorly coded API, where
updateUser
does not contain any pathvar :This can also be a problem when the request gives an error :
pathvars
andbody
will change, but not the content.How should we handle such cases ?
The text was updated successfully, but these errors were encountered: