Description
New Issue Checklist
- I am not disclosing a vulnerability.I am not just asking a question.I have searched through existing issues.I can reproduce the issue with the latest version of Parse Server and the Parse PHP SDK.
Issue Description
When setting liveQuery.classNames in the server config save all doesn't return object Id when saving more than one new objects. I assume that some sort of afterSave trigger is called that strips away the objectId. I've tested this against Parse Server 6. ObjectIds are returned when you saveAll on one object.
Since objectIds aren't returned you can't delete / save etc.
I believe the issue can be found by looking https://github.com/parse-community/parse-server/blob/alpha/src/RestWrite.js#L1607
Steps to reproduce
Actual Outcome
Objects save but objectId is missing
Expected Outcome
Objects save and return Id.
Parse PHP SDK
- SDK version:
2.0.0
- PHP version:
8.1
Server
- Parse Server version:
6.0.0
- Operating system:
Mac
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
Local
Database
- System (MongoDB or Postgres):
MongoDB
- Database version:
4.4
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
local
Activity
parse-github-assistant commentedon Apr 28, 2023
Thanks for opening this issue!
test: Failing test for parse-community#502
dplewis commentedon Apr 28, 2023
I created a Faliing test for this #503
I can't seem to replicate this on the JS SDK though.
afterSave
executes even if not set parse-community/parse-server#8520[-]SaveAll on new objects don't return objectId[/-][+]SaveAll on new objects does not return objectIds[/+]