You could create 3 separate interfaces, which a single repository could use.
Split things into logical groups:
Or create separate repositories, each with it's own interface.
My only question then becomes, are model relationships unnecessary? For example, my getPets() method simply creates a Client model and then uses the defined relationship to get the pets with $client->pets.
I figured a getPets() method in a PetsRepoInterface would return all pets, not client specific.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us
The Laravel portal for problem solving, knowledge sharing and community building.