Implement Forget Password Flow

EbrahimAli-RU commented 3 weeks ago

Fixes #77

Resolves # Used when the changes in the pull request indirectly resolve another issue.

[] Does not depend on other PRs
[x] Depends on other PR being merged first: #197

What kind of change does this PR introduce (check at least one)

[ ] Bugfix
[ ] Improvement
[x] New feature
[ ] Refactor
[ ] Infrastructure
[ ] Other (please specify)

How would you describe the changes in a changelog (1-2 lines)?

In the Forgot Password process, the user first requests a password reset by entering their registered Email. An OTP is then sent to the user for verification. Once the OTP is received, the user enters it along with a new password. This information is sent to the backend for validation and password update. If successful, the user is redirected to the login page to access their account with the new password.

Related Issues/PRs (optional)

Link to the relevant issue(s) or provide a clear description of the problem or feature being addressed.

How to test

[ ] Needs regression testing (add QA needed label)

Checklist

[x] I have tested these changes locally and they function as expected.
[ ] I have added or updated necessary documentation to reflect the changes.
[x] I have followed the project's coding style and guidelines.
[x] I have added appropriate test coverage to ensure the changes are functioning correctly.
[x] I have checked for any potential conflicts with other branches or pull requests.
[ ] I have updated necessary OpenAPI specs

Reviewer Request (optional)

If you have any specific requests or suggestions for reviewers, mention them here.

Screenshots (optional)

If applicable, provide any additional screenshots or GIFs that showcase the changes made in this pull request.

Demo Link (optional)

If applicable, provide a link to a live demo or deployment where the changes can be reviewed.

Known Issues (optional)

If there are any known issues or limitations with the changes made in this pull request, describe them here.

Additional Notes (optional)

Add any additional notes or comments you think are relevant to this pull request.

Deploy risk & follow up

Please assess risk & follow up on deployment of this PR. Elaborate your choice if selecting anything other than 'No risk'.

[x] No risk
[ ] Low
[ ] High

melon-ruet commented 3 weeks ago

Depends on other PR being merged first: https://github.com/CraftsmenLtd/BloodConnect/issues/185

This is not a PR link

melon-ruet commented 3 weeks ago

I can see all codes are under "mobile" directory. But forget password feature is also necessary in web app. Are we thinking about the core business logic in a single place?

EbrahimAli-RU commented 3 weeks ago

I can see all codes are under "mobile" directory. But forget password feature is also necessary in web app. Are we thinking about the core business logic in a single place?

Yes, vai, we are thinking of sharing common functionality between mobile and web applications since the web app is paused. We have a plan to move common functionality to a common directory after the first iteration. And I think we only can share auth-related functionality between mobile and web.

EbrahimAli-RU commented 3 weeks ago

Depends on other PR being merged first: #185

This is not a PR link

Updated.

CraftsmenLtd / BloodConnect