parse-community / parse-community/parse-server
Selecting authData doesn't work
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Issue Description
When querying _User and selecting authData, it's not contained in the response. The workaround is to select _auth_data_facebook instead. But authData should also work.
Steps to reproduce
Try in the API console, for example where={"username":"youruser"}&keys=authData vs where={"username":"youruser"}&keys=_auth_data_facebook
-
Server
- parse-server version: tested on 2.3.3, 2.8.4, 3.1.2
-
Database
- MongoDB version: 3.6.6, mlab
- Localhost or remote server? Both local and SashiDo
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
Reproduce the behavior in the API console using the two queries in the issue, comparing keys=authData with keys=_auth_data_facebook. Trace how Parse Server handles _User field selection and authData, then verify that selecting authData returns it as expected without breaking the existing workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100