parse-community / parse-community/parse-server
After Save User is not returning fields that I need
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- [ x ] I am not disclosing a vulnerability.
- [ x ] I am not just asking a question.
- [ x ] I have searched through existing issues.
- [ x ] I can reproduce the issue with the latest version of Parse Server.
Issue Description
After Save User is not returning fields that I need
the result will not come with this field, even if you put manually on AfterSave.
But if you put manually on AfterSave a property that doesn't exist on the database, it will return.
The login endpoint returns all the properties right.
Steps to reproduce
Create a property on Parse.User and Save a new Parse User filling this property.
Actual Outcome
Not returning properties like 'fullName'
Expected Outcome
Return properties that I need
Environment
Parse server Version 5.4.0 with MongoDB 5
Server
- Parse Server version: 5.40
- Operating system: Linux Ubuntu
- Local or remote host: Google Cloud
Database
- System (MongoDB or Postgres): Mongo
- Database version: 5.0.14
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): MongoDB Atlas
Logs
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
No source file, test, or entry point is named. Start by reproducing the issue with a Parse.User save and compare the returned fields with the login response and the AfterSave behavior. Done means persisted user properties such as fullName are returned after saving, with a regression test covering the response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, node.js
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100