For all messages besides "You're successfully logged in," users are directed to the wrong page. For example, after logging out or clicking the X on the message alert, users are directed to the "Sign In" page, although they should be directed to the "Log In" page (index.html).
Steps to Reproduce:
Log out of the system.
Click the X on the message alert.
Observe the redirection to the "Sign In" page instead of the "Log In" page.
Expected Behaviour:
Users should be directed to the "Log In" page (index.html) after logging out or dismissing the message alert.
Actual Behaviour:
Users are being directed to the "Sign In" page.
Suggested Fix:
Modify the redirection logic to ensure users are directed to the correct page (index.html) after logging out or dismissing the message alert.
Branch Strategy:
We should isolate features into different branches and merge them into the main branch only after thorough testing and review. Hence, helping to maintain a stable main branch and allowing for more efficient debugging and feature development.
I have resolved the issue where users were being redirected to the "Sign In" page instead of the "Log In" page after logging out or dismissing the message alert.
Details
Modified the redirection logic to ensure users are directed to the correct page (index.html) after logging out or dismissing the message alert.
For all messages besides "You're successfully logged in," users are directed to the wrong page. For example, after logging out or clicking the X on the message alert, users are directed to the "Sign In" page, although they should be directed to the "Log In" page (index.html).
Steps to Reproduce:
Expected Behaviour: Users should be directed to the "Log In" page (index.html) after logging out or dismissing the message alert.
Actual Behaviour: Users are being directed to the "Sign In" page.
Suggested Fix: Modify the redirection logic to ensure users are directed to the correct page (index.html) after logging out or dismissing the message alert.
Branch Strategy: We should isolate features into different branches and merge them into the main branch only after thorough testing and review. Hence, helping to maintain a stable main branch and allowing for more efficient debugging and feature development.