petrvs-repository-pattern

To standardize backend repository implementation, define expressive repository contracts and separate Eloquent read and write logic. Return composed data using DTOs instead of large associative arrays, keeping domain shapes stable and testable across your application.

The repository pattern standardizes data access by defining clear contracts between your application and persistence layer. Use DTOs for return data when domain shapes are stable, preventing large associative arrays and ensuring type-safe data transfer across module boundaries.

Register repository bindings by mapping contract interfaces to their concrete Eloquent implementations within the RepositoryServiceProvider. This wires your repository dependencies into the container, enabling seamless dependency injection across the application.

Write tenant-scoped integration tests by placing them in the prescribed test directories and executing Pest on modified repository and provider paths. This validates tenant-specific data isolation and ensures your repository behavior functions correctly within multi-tenant contexts.

Avoid injecting repositories directly into controllers except in a narrow read-only case. Injecting repositories directly into controllers creates tight coupling; route repository interactions through service classes to maintain proper separation of concerns and architectural boundaries.

Run PHPStan analysis on modified repository and provider paths by executing static analysis directly against your changed files. This quality safeguard detects type errors and architectural violations early, ensuring repository contracts and DTOs strictly adhere to prescribed standards.