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
If the user is logged in as user and then closes tab and reopens it from base url (here localhost:4321/) user is redirected to wrong screen causing error.
To Reproduce
Steps to reproduce the behavior:
Login as User
Close the tab
In new Tab enter base url (in this case localhost:4321)
Error is showned
Expected behavior
If we close the tab and reopen baseUrl localhost:4321 then if previously logged in user is (Type) user should redirect to user home screen.
Actual behavior
If we close the tab and reopen baseUrl localhost:4321 then error is shown.
Screenshots
wrong_redirect.mp4
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359
The text was updated successfully, but these errors were encountered:
@palisadoes unable to create PR due to commit workflow scripts checking linting rules. Due to changes of strict linting in #1700 around 271 occurrences of any datatype and linting issues need to be handled across repo before I could push a commit.
How should this be handled, Fix in this PR, separate issue to fix all occurrences of any datatype & linting issues or maybe easing of strict linting rules and then eventually eradicate linting issues to implement strict linting?
Describe the bug
To Reproduce
Steps to reproduce the behavior:
localhost:4321
)Expected behavior
If we close the tab and reopen baseUrl
localhost:4321
then if previously logged in user is (Type) user should redirect to user home screen.Actual behavior
If we close the tab and reopen baseUrl
localhost:4321
then error is shown.Screenshots
wrong_redirect.mp4
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359
The text was updated successfully, but these errors were encountered: