Comments (5)
My opinion: The repository pattern is the devil and should be avoided. It's taking SOLID to unnecessary levels with an ORM framework. Otherwise just store interfaces in Contracts/
from laravel-best-practices.
We need more than "I like it". In general there is a significant positioning against repositories in Laravel, mainly because it relies in an Active record pattern, and its advantages are lost when Models are isolated in Repos.
In terms of Models, Laravel's style mean the use of Concerns to compose behavoir. That means that every functionality should also be exposed explicitly in Repos, what makes things complex.
from laravel-best-practices.
but for me, i like using repo than interfaces
from laravel-best-practices.
Hello everyone,
adding my 2-cent to the discussion about repo patterns:
From working on a larger, aged applications with repos, the repos didn't add much benefit IMHO. The repo pattern seems to work better for frameworks without strong ORM or even completely without any ORM. With Laravel most of the value from repos comes from abstracting a few setters/getters away and being more DRY. The setters and getters are covered with Eloquent pretty good already I think. The DRY part can easily achieved with an actions nicely I would argue. Can you share where you see the advantages @jocelinkisenga?
Cheers,
Peter
from laravel-best-practices.
how that things can get complex? give your real example of using repo pattern
from laravel-best-practices.
Related Issues (20)
- What PHP to JS package is recommended? HOT 4
- How about throw exceptions? HOT 5
- Do not get data from the .env file directly, why? HOT 2
- What about laravel Resources? HOT 3
- Wrong return type? HOT 1
- PSR-12 HOT 3
- What about translation variables? HOT 2
- Best
- Converting from and back to json HOT 1
- Validation FormRequest HOT 1
- Looking for the repo owner HOT 8
- Typo Issue in example (Don't repeat yourself (DRY)) HOT 2
- Store dates in the standard format. Use accessors and mutators to modify date format HOT 11
- Seeder in singular -> Good, Seeder in plural -> bad (naming-conventions) HOT 2
- Recommended route name conflict?
- A tool that enforces all these best practices HOT 1
- Change test case methods to snake_case HOT 1
- Query Parameter Validation HOT 1
- La
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from laravel-best-practices.