parse-community / parse-community/parse-server
Add a email address change workflow
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently there is not built-in workflow for changing an email address like there is for email verification or password reset.
Feature / Enhancement Description
Adding a built-in workflow for changing the email address can leverage the already existing mechanisms for email verification / password reset.
Example Use Case
- User requests to change the email.
- Parse Server sends email to old email address.
- User opens email link and gets to website to enter a new email address.
- Parse Server changes email address in DB and sends confirmation email to old and new email address.
Alternatives / Workarounds
Manually implementing a workflow.
3rd Party References
(none)
Note
Before anyone starts to work on a PR, it makes sense to wait until the new PagesRouter is merged where this kind of workflow is easier to implement. In addition, any implementation in the current PublicAPIRouter will become obsolete once the PagesRouter goes out of experimental state - which should be fairly soon.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing email verification and password reset mechanisms, then inspect the PagesRouter work in pull request #7128 before choosing an implementation path. The workflow should support requesting a change, verifying through the old address, updating the database, and sending confirmations to both addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- authentication, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100