Closed
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.
Issue Description
As reported by @Moumouls in PR #7344:
On our production system recently, we faced some weird random issue on types shared between custom and auto gql schema.
The issue come from the merge system that i designed, it seems that some JS ref object mess up during merge process.
Also i removed the stichSchema with merge directive because it seems use less when a code custom schema is used.
Also i do not succeed reproducing the issue on Parse server test and even in our production test suite. My team only succeed to reproduce the issue with manual e2e testing, and this fix resolve the random issue.
Steps to reproduce
Actual Outcome
Expected Outcome
Failing Test Case / Pull Request
- 🤩 I submitted a PR with a fix and a test case.
- 🧐 I submitted a PR with a failing test case.
Environment
Server
- Parse Server version:
FILL_THIS_OUT
- Operating system:
FILL_THIS_OUT
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
FILL_THIS_OUT
Database
- System (MongoDB or Postgres):
FILL_THIS_OUT
- Database version:
FILL_THIS_OUT
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
FILL_THIS_OUT
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
FILL_THIS_OUT
- SDK version:
FILL_THIS_OUT