Feature/132 jpa repositories#151
Merged
Merged
Conversation
Add additional query to find player in specific lobby
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Context
This PR contains the addition of repository classes for entity classes.
Description
Currently the repositories are quite small and only contain the lobby and the player entities. With the aggregating Lobby architecture of the DB, it should be possible to retrieve all the other information through the Lobby object itself.
If this is a mistake or lacking, more will be added in the next PR where the persistence mapping feature is implemented
Changes in the code base
Changes outside the code base
N/A
Additional information
N/A