docs: corriger références ADR dans CLAUDE.md

Corrections des numéros d'ADR décalés :
- ADR-014 → ADR-012 (Frontend Mobile)
- ADR-016 → ADR-014 (Organisation Monorepo)
- ADR-012 → ADR-010 (Architecture Backend)
- ADR-013 → ADR-011 (ORM et Accès Données)
- ADR-015 → ADR-013 (Stratégie Tests)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
jpgiannetti
2026-02-01 15:08:51 +01:00
parent 852f6d5e16
commit c3abdd74af

View File

@@ -8,7 +8,7 @@ RoadWave is a geo-localized audio social network for road users (drivers, pedest
**Tech Stack**: **Tech Stack**:
- Backend: Go 1.21+ with Fiber framework - Backend: Go 1.21+ with Fiber framework
- Mobile: Flutter (see [ADR-014](docs/adr/014-frontend-mobile.md)) - Mobile: Flutter (see [ADR-012](docs/adr/012-frontend-mobile.md))
- Database: PostgreSQL 16+ with PostGIS extension - Database: PostgreSQL 16+ with PostGIS extension
- Cache: Redis 7+ with geospatial features - Cache: Redis 7+ with geospatial features
- Auth: Zitadel (self-hosted IAM) - Auth: Zitadel (self-hosted IAM)
@@ -32,11 +32,11 @@ This is a monorepo organized as follows:
- Backend step definitions: `backend/tests/bdd/` - Backend step definitions: `backend/tests/bdd/`
- Mobile step definitions: `mobile/tests/bdd/` - Mobile step definitions: `mobile/tests/bdd/`
See [ADR-016](docs/adr/016-organisation-monorepo.md) for monorepo organization rationale. See [ADR-014](docs/adr/014-organisation-monorepo.md) for monorepo organization rationale.
## Backend Architecture ## Backend Architecture
**Modular monolith** with clear module separation ([ADR-012](docs/adr/012-architecture-backend.md)): **Modular monolith** with clear module separation ([ADR-010](docs/adr/010-architecture-backend.md)):
``` ```
backend/internal/ backend/internal/
@@ -52,7 +52,7 @@ backend/internal/
**Module pattern**: Each module follows `handler.go``service.go``repository.go`. **Module pattern**: Each module follows `handler.go``service.go``repository.go`.
**Database access**: Uses `sqlc` ([ADR-013](docs/adr/013-orm-acces-donnees.md)) for type-safe Go code generation from SQL queries. This allows writing complex PostGIS spatial queries while maintaining compile-time type safety. **Database access**: Uses `sqlc` ([ADR-011](docs/adr/011-orm-acces-donnees.md)) for type-safe Go code generation from SQL queries. This allows writing complex PostGIS spatial queries while maintaining compile-time type safety.
## Development Commands ## Development Commands
@@ -76,7 +76,7 @@ Services after `make docker-up`:
### Testing ### Testing
**Test Strategy** ([ADR-015](docs/adr/015-strategie-tests.md)): **Test Strategy** ([ADR-013](docs/adr/013-strategie-tests.md)):
- Unit tests: Testify (80%+ coverage target) - Unit tests: Testify (80%+ coverage target)
- Integration tests: Testcontainers (for PostGIS queries) - Integration tests: Testcontainers (for PostGIS queries)
- BDD tests: Godog/Gherkin (user stories validation) - BDD tests: Godog/Gherkin (user stories validation)
@@ -182,9 +182,9 @@ All technical decisions are documented in Architecture Decision Records (ADRs) i
- [ADR-002](docs/adr/002-protocole-streaming.md): Streaming protocol (HLS) - [ADR-002](docs/adr/002-protocole-streaming.md): Streaming protocol (HLS)
- [ADR-005](docs/adr/005-base-de-donnees.md): Database (PostgreSQL + PostGIS) - [ADR-005](docs/adr/005-base-de-donnees.md): Database (PostgreSQL + PostGIS)
- [ADR-008](docs/adr/008-authentification.md): Authentication (Zitadel) - [ADR-008](docs/adr/008-authentification.md): Authentication (Zitadel)
- [ADR-012](docs/adr/012-architecture-backend.md): Backend architecture (modular monolith) - [ADR-010](docs/adr/010-architecture-backend.md): Backend architecture (modular monolith)
- [ADR-013](docs/adr/013-orm-acces-donnees.md): Data access (sqlc) - [ADR-011](docs/adr/011-orm-acces-donnees.md): Data access (sqlc)
- [ADR-016](docs/adr/016-organisation-monorepo.md): Monorepo organization - [ADR-014](docs/adr/014-organisation-monorepo.md): Monorepo organization
**When making architectural decisions**, check if there's an existing ADR or create a new one following the established pattern. **When making architectural decisions**, check if there's an existing ADR or create a new one following the established pattern.