Related Issue:
Closes #85
Closes #5 - this feature was already implemented when I started working on this issue so that issue can also be closed - please verify though.
Description:
Users can now sign in through the header sign in form, after choosing to "continue without signing in".
You should be able to sign in through both the main authentication page and the header and both ways of signing in will be authenticated.
Also changed the formatting of the fields to ensure that both the format and functionality was consistent across both forms of signing in. Consequently, this resolves the capitalisation of the 'P' on the main authentication page, noted in issue #116 .
Testing:
Tests have not been written as testing has not been set up yet.
However, the functionality can be manually tested by checking for the following:
[x] Sign in via header form after clicking "Continue without sign in"
[x] Sign out and sign back in from main authentication page
[x] Enter a character into one of the fields on the main authentication page, then click "Continue without sign in" and sign in via the header form
[x] Latest master merged/rebased into your feature branch
[x] Tests covering all changes
[x] Meets the projects coding conventions
[x] No out of scope changes
[x] @Mentioned any relevant team members
[x] Included a relevant gif (search here for inspiration)
Related Issue: Closes #85 Closes #5 - this feature was already implemented when I started working on this issue so that issue can also be closed - please verify though.
Description: Users can now sign in through the header sign in form, after choosing to "continue without signing in". You should be able to sign in through both the main authentication page and the header and both ways of signing in will be authenticated. Also changed the formatting of the fields to ensure that both the format and functionality was consistent across both forms of signing in. Consequently, this resolves the capitalisation of the 'P' on the main authentication page, noted in issue #116 .
Testing: Tests have not been written as testing has not been set up yet. However, the functionality can be manually tested by checking for the following: