parse-community / parse-community/parse-dashboard
Can not save new _User object after deleting field value
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
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.
- I can reproduce the issue with the latest version of Parse Dashboard.
Issue Description
Not able to save or create new objects after deleting one of the field values, using del key after selecting that field cell.
Steps to reproduce
- Click on add new row button
- set value in any field
- select that field and press
delkey, that should unset that field - (if any required field, then fill those first) save new row.
Actual Outcome
Can not save new row, getting error You cannot use [object Object] as a query parameter.
Expected Outcome
should be able to save new row.
Pull Request
- PR: #
FILL_THIS_OUT
Environment
Dashboard
- Parse Dashboard version:
2.1.0 - Browser (Safari, Chrome, Firefox, Edge, etc.):
Chrome - Browser version:
Version 92.0.4515.107 (64-bit)
Server
- Parse Server version:
4.5.0 - Operating system:
Ubuntu 20.04.2 LTS - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
local
Database
- System (MongoDB or Postgres):
MongoDB - Database version:
3.3 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
remote host
Logs
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 reproducing the add-new-row flow in Parse Dashboard: enter a value, select the field, press Delete, and save with required fields filled. Trace the new-row save path to identify how the deleted field is represented, then verify that saving succeeds without the query-parameter error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- database, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100