Add 7 ADRs documenting backend architecture decisions
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# ADR 0007: Removal of Legacy Route Directories (v1, v2, v3)
|
||||
|
||||
**Date:** 2026-04-26
|
||||
**Status:** Proposed
|
||||
|
||||
## Context
|
||||
|
||||
The `src/routes/` directory contains three legacy subdirectories (`v1/`, `v2/`, `v3/`) alongside the active `api/` directory. These are backup snapshots of earlier API iterations, kept during the migration to the current domain-based structure. They are not mounted in the application and serve no runtime purpose.
|
||||
|
||||
Their presence:
|
||||
- Creates confusion about which routes are active.
|
||||
- Adds noise to `grep` and IDE navigation.
|
||||
- Risks accidentally referencing stale logic.
|
||||
|
||||
## Decision
|
||||
|
||||
Remove `v1/`, `v2/`, and `v3/` directories once the following is confirmed:
|
||||
- No active code references them (direct imports or dynamic requires).
|
||||
- Their content has been superseded by the equivalent routes under `src/routes/api/`.
|
||||
|
||||
## Consequences
|
||||
|
||||
- **Positive:** Cleaner repository. Only active routes remain.
|
||||
- **Risk:** If any code path still references these directories, removal would cause a runtime error. Verify with `grep -r "routes/v[123]"` before deleting.
|
||||
- **Status rationale:** Marked as *Proposed* rather than *Accepted* until the verification step is completed and the deletion is committed.
|
||||
Reference in New Issue
Block a user