Skip to content
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

Redirect even when authData is present #505

Closed
wants to merge 1 commit into from
Closed

Redirect even when authData is present #505

wants to merge 1 commit into from

Conversation

rrjohnson85
Copy link

@rrjohnson85 rrjohnson85 commented May 17, 2019

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Currently if authData is present, the canActivate guard will not store the redirect route path in localStorage.

Issue Number: #491

What is the new behavior?

Now, canActivate will attempt to store the redirect route path in local storage based on authData and the value of the expiry key.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

@rrjohnson85
Copy link
Author

@neroniaky do docs need updated to describe the behavior?

Currently if authData is present, the canActivate guard will not redirect to the redirect path stored in localStorage.

Now, canActivate will attempt to redirect based on authData and the value of the expiry key.
@neroniaky
Copy link
Owner

@rrjohnson85 thanks for this PR. I don't think we have anything in the docs about this behaviour, but a clarification would be great.

@rrjohnson85 rrjohnson85 closed this by deleting the head repository Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants