parse-community / parse-community/parse-server-push-adapter
Break up push adapter APIs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
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
With web, expo, APNS and Firebase push support, the push adapter forces additional dependencies on deployments that may not need it. In fact, some of these APIs are mutually exclusive.
Feature / Enhancement Description
Break up the push adapter into individual adapters per API, so that developers add only push support for APIs that they actually need.
Similar to database adapters. This requires a change on the Parse Server side as well.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the current push adapter integrations for web, Expo, APNS, and Firebase, then examine how Parse Server consumes the adapter. Done means the APIs are split into individual adapters so deployments can install only the push support they need, with the required Parse Server change accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100