We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On invalid refresh token, the error is unmanaged
The router should redirect to the login page, deleting the available tokens.
Nothing happens, while backend responds with 400 - bad request
"@gngt/material": "^7.0.0-alpha.5"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug, feature request, or proposal:
On invalid refresh token, the error is unmanaged
What is the expected behavior?
The router should redirect to the login page, deleting the available tokens.
What is the current behavior?
Nothing happens, while backend responds with 400 - bad request
What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Gngt, OS, TypeScript, browsers are affected?
"@gngt/material": "^7.0.0-alpha.5"
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: