parse-community / parse-community/parse-server
Improve dynamic updating of Parse Server Config
Open
Nobody has claimed this yet.
type:feature
- 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, Parse Server config can be updated via Parse.Server = newConfig, which is not ideal as:
- Global
Parse.Servershould probably not be writeable - No verification of the new config
Feature / Enhancement Description
Allow new Parse.Server hooks with the prefix of set, which allow for dynamic change of config. Such as:
Example Use Case
Parse.Server.setSilent(false);
Alternatives / Workarounds
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
The issue names no files, tests, or entry points. Start by tracing how Parse.Server is defined and how its current assignment path handles configuration, then determine where set-prefixed hooks and verification belong. Done should include a defined dynamic-update API that supports the example use case without direct replacement of the global configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100