-
Notifications
You must be signed in to change notification settings - Fork 96
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
response interceptor not working for response with 400, 500 status code #27
Comments
What i am trying to do is that dispatch action(for showing notification UI) when request is failed. (get 400 or 500 response)
Note that I am trying to show global notification UI for all requests failure. |
I think @svrcekmichal latest commit for #26 now passes the dispatch method to the interceptors. Can you try that and let us know if that works? |
Hi @SergeyKorchevskiy you can use interceptor two ways:
Please try it the second way, and let us know if it didn't work. I will try to create some tests tomorrow and commit them to package to better show usage |
@svrcekmichal I finally found the solution like below by myself.
I can dispatch action for showing error notification in Thanks! |
Well, you can override |
@svrcekmichal Okay, I will wait for your solution. |
@SergeyKorchevskiy Hi, little bit late, but I have created tests for interceptors and they seem to work fine. I have added them in branch feature/tests in this file. Please give it a look and if you don't make it work, please send you code and I can check if you don't have any typo or another mistake |
@SergeyKorchevskiy closing for know, if you still have issue just write and i will reopen this |
Hi @svrcekmichal, Could you provide an example of implementation with OAuth2 ? |
Hi, is http status code available somewhere in case of interceptor error handler ? |
Check my answer in #87 |
Hello @svrcekmichal
I've confirmed that response interceptor is not working when the response's httpStatus code is not 200.
Otherwise it seems like working with 200 status codes.
Would you please check this?
Thanks,
Sergey
The text was updated successfully, but these errors were encountered: