parse-community / parse-community/docs
📙 Possible incongruity on beforeLogin cloudCode documentation
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 507
- PR merge metrics
- No merged PRs in 30d
Description
I was reading the parse cloud code docs on this part and saw :
The user is not available on the request object - the user has not yet been provided a session until after beforeLogin is successfully completed
And after doing some tests, I realized that this information was incomplete, because I got this as answer:
Another information that can be considered relevant is that parse user object is not the original request one, but the one from database and I don't know why, and i think this cloudCode run beforeSave ParseUser.
I checked the code and couldn't really understand the code, since I'm a newbie 🤣. but I would like to know if what I perceived proceeds.
Contributor guide
No contributing guide indexed for this repository
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
Read the linked Cloud Code guide's “Some considerations to be aware of” section first, then reproduce the reported beforeLogin behavior and compare it with the current wording. Done means documenting the confirmed request and user-object behavior, including whether the beforeSave timing belongs in this explanation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100