parse-community / parse-community/parse-server
Sending unsaved Parse Objects to Client
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem? Please describe.
I use Parse Server as App-Backend and store some informations in the Parse DB. Other informations are received live from third party backends via cloud-code. To unify the communication between the Parse Backend and the App I tried to generate temporary Parse Objects to send these Objects to the App but I aren't allowed to store them in the Parse DB. When I try to send the object to the App I got the error "Cannot create a pointer to an unsaved ParseObject"
Describe the solution you'd like
Send the Objects to the App (perhaps with a "temp_xyz" objectId like the local objectId)
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 file, test, or entry point is named in the issue. Start by tracing how Parse Server serializes and sends Parse Objects, then define the expected behavior for unsaved objects and verify that temporary objects can be returned without persistence or invalid pointers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100