feat(nano)!: use In-Memory MongoDB in lieu of PouchDB to power Data Services #613
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ervices BREAKING CHANGE: Since PouchDB is no longer being used, any pre-existing hyper nano data services will not work, and will need to be re-seeded
TillaTheHun0
force-pushed
the
tillathehun0/nano-mongo-in-memory
branch
from
2537291
to
d90e96a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: Since PouchDB is no longer being used, any pre-existing hyper nano data services will not work, and will need to be re-seeded
This mitigates the esoteric nature of PouchDB indexes and instead uses the more general purpose MongoDB and corresponding adapter. Since most hyper Service Framework users use MongoDB, this makes sense to use in hyper-nano
Also bumps all deps to latest.