medikoo / medikoo/dbjs-persistence
Automatic resolution of storage type
@medikoo is already working on this.
Since Jan 12, 2016.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
/cc @kamsi
Currently when we want to get given value we need to specify which storage we use direct, computed or reduced, but after some improvements engine may intelligently resolve out of provided id (or path) which storage handles given value.
For now wether query is about computed path can be resolved from registered indexes, for reduced path tracking will have to be improved as custom reducers are not marked internally.
Additionally it would be good store persistently somewhere all initialized indexes. Currently indexes are known only known from loaded programmatical configuration.
If given index is initialized in some other previous setup, engine will not be aware that such index were handled.
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.
Assessment
This issue has not been assessed yet.