You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2021. It is now read-only.
response object is returned to fulfill view promise or other subscribers
I do not want view to catch the error nor to process the result because in 3. action was taken
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
The text was updated successfully, but these errors were encountered:
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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: