-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixed more readable #168
base: master
Are you sure you want to change the base?
fixed more readable #168
Conversation
👎 Using the repository pattern with Laravel goes against its core ORM design |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think It it better approach
This is a good explanation as why it's not a good idea in 99.9% of Laravel projects |
In the context of Laravel, Repository provides the very same functionality and isolation than Eloquent Models do. Using it is duplicating behavior already present, and screwing up all the convention provided by an standard tool like Eloquent and the framework itself. Everybody knows Eloquent, it has a CONVENTION that a Repository will provide BY CONFIGURATION, following its own standards. |
What are you approaching to? :) Can you explain your POV? |
No description provided.