parse-community / parse-community/parse-server
Email verification calls (beforeFind) / (beforeSave) triggers without informing that the request is an email verification.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
when Email verification calling triggers the values contained in request is master = false, also user and maintenance are not defined in request, so, it'll be best to do add request.maintenance to the request in the triggers or a new key like request.emailVerification as boolean to have know if the request from email verification or not.
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 tracing the email-verification flow and how it invokes the beforeFind and beforeSave triggers. Check what request context those triggers currently receive; done means a trigger can reliably identify that the request came from email verification, using request.maintenance or a request.emailVerification boolean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100