Skip to content

feat: update forgotten password form

Rémi PAILHAREY requested to merge 480-ui-page-mot-de-passe-oublie-a-faire-en-v3 into dev

Related to #480 (closed)

What does this MR do and why?

Updates this form style to V3

Removed footer

Used FormGroup instead of UntypedFormGroup

Removed the case where user visits the reset page with a token while connected

Screenshots or screen recordings

Before After
image image
image.png image.png

How to set up and validate locally (or on alpha)

Make sure your profile email is valid (ex: pnom@grandlyon.com)

Click "Mot de passe oublié" on connection page

try different invalid email, then your real email

Visit http://localhost:4200/reset-password?token=wrongtoken, you should get an error notifcation when you submit a new password

Click the link received in your mail box, try different things :

  • Wrong password format
  • Valid password but confirmation is different
  • Valid password + valid confirmation

MR acceptance checklist

To be completed by the chosen reviewer.

Quality Bugs - Code Smells

  • For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
  • I have made sure that the sonar quality coverage is up to standards.
  • I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
  • I have tested this MR in all supported browsers or determined that this testing is not needed.
  • I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.

Performance, reliability and availability

  • I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
  • I have considered the scalability risk based on future predicted growth.

Documentation

  • The MR is named after the desired squash commit to feed the changelog linked to the current milestone.
  • I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.

Security Security Rating

  • I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.

Related to #480 (closed)

Edited by Rémi PAILHAREY

Merge request reports