crud-repository

What problem does it solve?

Enforces consistent repository patterns to prevent scattered, insecure, or inconsistent data access implementations by establishing BaseRepository conventions, tenant scoping, pagination, and unified error semantics so services remain testable and transaction-safe.

Core Features & Use Cases

• Rule Set & Linting: Declarative rules for file naming, method signatures, imports, tenant scope checks, pagination, and soft-delete behavior.
• Templates & Patterns: Ready-to-use interface+implementation templates, TenantScope and Paginate helpers, and constructor conventions to simplify DI and transaction propagation.
• Use Case: Migrate ad-hoc Go data access code into a consistent BaseRepository pattern to ensure all queries include tenant_id, list endpoints support paging, and services can translate repository errors into HTTP semantics.

Quick Start

Validate the repository files under internal/repository and pkg/corex/db/persistence/repository against the crud_repository rules and report any violations.