parse-community / parse-community/parse-server
Remove config `databaseURI`, `databaseOptions`, `collectionPrefix` in favor of `databaseAdapter`
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
- Report security issues confidentially.
- Any contribution is under this license.
- Before posting search existing issues.
Current Limitation
There are databaseURI , databaseOptions, collectionPrefix and databaseAdapter as config options. That is redundant:
- It seems to be that
databaseOptionstakes some Parse Server custom options and some options that are then passed directly to the DB client. This requires complex filtering. - There are many native DB client options that are not supported by Parse Server because Parse Server validates native DB client options before passing them on. This validation is unnecessary and causes Parse Server to chronically lag behind supporting the latest DB driver options.
Feature / Enhancement Description
- Remove
databaseOptionsand move the Parse Server native options, likeenableSchemaHooks,schemaCacheTtl, etc. into a new sub keyDatabaseAdapter.options. The DB client options can already be passed viaDatabaseAdapter.mongoOptionsfor example. It may make sense to keepdatabaseOptionsfor Parse Server native options if it turns out too complex to pass them via the DB adapter, as it affects features like schema hooks that are implemented in Parse Server core, rather than the DB adapter. - Remove option
databaseURI, as this can already be provided viaDatabaseAdapter.uri. - Remove any obsolete logic like parsing the
databaseURIstring to auto-determine which DB the URI points to, to then automatically load the correct adapter.
This is in line with the larger plan to move all DB adapters out of the Parse Server core repository.
Example Use Case
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
No files, tests, or concrete entry points are named. Start by tracing configuration handling for databaseURI, databaseOptions, collectionPrefix, and databaseAdapter, then map the adapter-loading and URI-detection logic. Done means the redundant options and obsolete auto-detection are removed while the requested adapter option behavior is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100