parse-community / parse-community/parse-dashboard
feat(file): add option to delete file from storage
Open
Nobody has claimed this yet.
type:feature
- 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
Any operation on file (delete document containing file, use Delete/Replace File) in Parse Dashboard doesn't delete the file.
Steps to reproduce
- Upload a file.
- Replace/delete that file through Parse Dashboard.
Actual Outcome
Checking MongoDB dashboard, the file is still there (in fs.chunks and fs.files)
Expected Outcome
File should be deleted
Pull Request
- PR: #
FILL_THIS_OUT
Environment
Dashboard
- Parse Dashboard version:
2.1.0 - Browser (Safari, Chrome, Firefox, Edge, etc.):
Edge - Browser version:
Version 92.0.902.73 (Official build) (64-bit)
Server
- Parse Server version:
4.5.0 - Operating system:
Windows 10 - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
Heroku
Database
- System (MongoDB or Postgres):
MongoDB - Database version:
4.4 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
MongoDB Atlas
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
Reproduce the issue in Parse Dashboard with MongoDB and inspect the Delete/Replace File flow; run npm run dev if browser errors or source maps are needed. Done means deleting or replacing a file removes its corresponding records from fs.chunks and fs.files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- databases, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100