parse-community / parse-community/parse-server
Add 'include' and 'excludeKey' to user endpoints
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
Some user endpoints like login/signup and retrieving current user ("users/me") do not support basic query parameters such as 'include' and 'excludeKey'.
For example https://parseserver.com/parse/users/me?include=className would return the same response exactly as https://parseserver.com/parse/users/me
I believe this behavior also happens in the login/signup endpoints.
Feature / Enhancement Description
Add support for these keys in these endpoints.
Example Use Case
You may have a user that has a pointer to some class and you want to retrieve that pointer's field data along with the user..
Alternatives / Workarounds
There are none
3rd Party References
-
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 locating the handlers and endpoint tests for login, signup, and retrieving the current user (users/me), then trace how query parameters are processed for user responses. The work is done when include and excludeKey affect responses consistently on those endpoints, with tests covering the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100