Oauth2 + repositpory + business #16
Open
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
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.
I made an implementation like this in one of my projects, I found it interesting to have something ready for posterity.
I made the implementation of two new layers.
The Business layer takes care of the entire business rule, and communicates with the repository, which in turn is solely responsible for querying the database.
I also implemented an authentication model using Auth2, with the help of a lib from The League PHP guys.
I also implemented a helper, with a module just to include helpers in the project, as well as a message-only area, and enuns, to facilitate the creation and organization of enums within a project.