This repository has been archived by the owner on Sep 12, 2021. It is now read-only.
Move persistence based API into a separate project #419
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
It's often misleading that the persistence based API is integrated into the core project, because it's not really required by the core. The provides API is only one possible implementation which helps to start a new application quicker. Therefore this pull request moves the persistence based API into a separate project and provides a in-memory implementation for the auth info implementations. It's now also possible to provide different drop-in replacements for the persistence layer instead of creating a separate seed template for every persistence type(reactivemongo, slick, ...).
akkie
added a commit
that referenced
this pull request
Oct 30, 2015
Move persistence based API into a separate project
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It's often misleading that the persistence based API is integrated into the core project, because it's not really required by the core. The provides API is only one possible implementation which helps to start a new application quicker. Therefore this pull request moves the persistence based API into a separate project and provides a in-memory implementation for the auth info implementations. It's now also possible to provide different drop-in replacements for the persistence layer instead of creating a separate seed template for every persistence type(reactivemongo, slick, ...).