parse-community / parse-community/parse-server
LiveQuery support for the Parse Config
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
Currently there's no way to listen for a changes on Parse Config.
Feature / Enhancement Description
If LiveQuery can start support Parse Config this will be awesome as it can listen for changes on the configuration and apply them runtime. Firebase Remote Config for example uses pulling, where the LiveQuery can make it even better.
Firebase pulling:
val remoteConfig = Firebase.remoteConfig
val configSettings = remoteConfigSettings {
minimumFetchIntervalInSeconds = 3600
}
remoteConfig.setConfigSettingsAsync(configSettings)
Example Use Case
Feature flags is a good candidate for example use case. Developers can store feature flags data in Parse Config and the apps can
listen for changes using the LiveQuery and trigger features server side.
Alternatives / Workarounds
- Custom implementation using pulling and using platform specific SDKs Parse Config APIs.
- Creating custom Parse class handling the remote configuration or feature flags (this invalidated the Parse Config feature) and use the LiveQuery with it.
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
Start by examining the existing Parse Config and LiveQuery behavior described in the issue. No files, tests, or implementation entry points are named, so first identify where each feature is handled and how changes are propagated. Done should provide a defined way for clients to receive Parse Config changes at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100