Repository design pattern done right in Laravel

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1339
    rintoug
    Participant

    Repository design pattern done right in Laravel

    #1340
    WitteStier
    Guest

    “Repositories shouldn’t create or update data, but should only be used to retrieve data”

    A repository is a collection like object. So once again, it can create, update and delete.

    Why is it that as soon laravel is involved, design patterns are misunderstood and are implemented wrong.

    Please all of you laravel users, stop thinking that eloquent is o good thing. It’s an antipattern. And stop using repositories to hide your eloquent mess.

    Please read https://www.martinfowler.com/eaaCatalog/ and stop using titles like “*** patterns done the right way”.

    #1341
    psihius
    Guest

    Paywall.

    #1342
    hapanda
    Guest

    > Repositories **shouldn’t** create or update data, but should **only** be used to retrieve data

    Is there any explanation in article about that?

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.