Open barocsi opened 7 years ago
I have similar scenario aswell.
In OAuth2, if the refresh token is expired (which I will come to know when I send the request to server & get the response), I need to redirect the user to login page & don't want the interceptor chain(in the reverse order) to be executed.
So, there should be a provision to cancel the interceptor chain execution (interceptAfter
) in the reverse order
The case is the following:
in non typescript scenarios I was simply injected a property handled = true in the response object so the view/controller knew there is nothing further to do with the error message.
What is the best pattern to intercept and prevent bubbling but fulfill view/controller promises or observer subscribers?
Thanks