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
Actually userSignedIn() method can be used when is called only
userSignedIn can be a observable, this ensures when the data changes to false, subscribers callbacks can be executed
In my app when user logout, is difficult handle with this method
Angular-Token version: ^7.0.1 Angular version: 7.1.4
Bundler
Browser:
The text was updated successfully, but these errors were encountered:
Hey @ArmandoPerdomo you could give the RC of 7.1.0 a try, which has this build in.
Sorry, something went wrong.
I tried, but you have added this feature yet?
No branches or pull requests
I'm submitting a...
Current behavior
Actually userSignedIn() method can be used when is called only
Expected behavior
userSignedIn can be a observable, this ensures when the data changes to false, subscribers callbacks can be executed
What is the motivation / use case for changing the behavior?
In my app when user logout, is difficult handle with this method
Environment
Angular-Token version: ^7.0.1
Angular version: 7.1.4
Bundler
Browser:
The text was updated successfully, but these errors were encountered: