Skip to content

Conversation

hareom284
Copy link

No description provided.

@JohnnyWalkerDigital
Copy link
Contributor

👎 Using the repository pattern with Laravel goes against its core ORM design

Copy link

@zawzawwin-dev zawzawwin-dev left a 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

@JohnnyWalkerDigital
Copy link
Contributor

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

https://www.youtube.com/watch?v=giJcdfW2wC8

@carlos-mora
Copy link

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.

@carlos-mora
Copy link

I think It it better approach

What are you approaching to? :) Can you explain your POV?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants