parse-community / parse-community/parse-server
Support passing additional params with file save/upload POST request and expose those in beforeSaveFile/afterSaveFile
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
No official support.
Feature / Enhancement Description
This is the server-side feature request to support the relevant functionality of the client SDK feature requests:
https://github.com/parse-community/Parse-SDK-Android/issues/1201
https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1766
Example Use Case
See linked client sdk bugs
Alternatives / Workarounds
Custom schemes to pass additional params via headers, or mimicking the JS SDK behavior and recoding the file into a json format with additional metadata/tags. See linked client sdk bugs for details
3rd Party References
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
Read the linked Android and iOS SDK issues first to understand the requested parameter behavior. Then trace parse-server's file upload POST handling and the beforeSaveFile/afterSaveFile hooks; done means additional parameters are accepted and exposed consistently in both hooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100