[37.2.1] Rename LawNet BFF API routes under /api/lawnet #53

New issue

Closed

opened 2026-06-14 10:52:31 +02:00 by dernbu · 0 comments

dernbu commented

2026-06-14 10:52:31 +02:00

Owner

Parent

#49

Objective

Rename the existing LawNet BFF API routes into a LawNet-specific namespace before adding the PostgreSQL storage provider.

This is intentionally a separate review step so the route/API refactor can be merged before the larger #49 PostgreSQL implementation.

Scope

Move the current LawNet-backed judgment API routes under /api/lawnet/*.
Preserve the current response contract and existing filesystem-backed behavior.
Update route references in tests, fixtures, and artifact URLs as needed.
Keep the existing LawnetStore interface behavior intact.
Ensure the route namespace leaves room for future eLitigation-specific or combined judgment APIs.

Out of scope

PostgreSQL storage provider.
Flyway schema changes.
Database integration tests.
UI/frontend changes beyond any route references required for tests or fixtures.
Malformed source-record/reconciliation handling.

Done when

The current filesystem-backed LawNet BFF behavior works through /api/lawnet/* routes.
Old route references used by tests/fixtures are updated.
Existing filesystem storage tests still pass.
This refactor can be reviewed and merged independently before the rest of #49.

## Parent #49 ## Objective Rename the existing LawNet BFF API routes into a LawNet-specific namespace before adding the PostgreSQL storage provider. This is intentionally a separate review step so the route/API refactor can be merged before the larger #49 PostgreSQL implementation. ## Scope - Move the current LawNet-backed judgment API routes under `/api/lawnet/*`. - Preserve the current response contract and existing filesystem-backed behavior. - Update route references in tests, fixtures, and artifact URLs as needed. - Keep the existing `LawnetStore` interface behavior intact. - Ensure the route namespace leaves room for future eLitigation-specific or combined judgment APIs. ## Out of scope - PostgreSQL storage provider. - Flyway schema changes. - Database integration tests. - UI/frontend changes beyond any route references required for tests or fixtures. - Malformed source-record/reconciliation handling. ## Done when - The current filesystem-backed LawNet BFF behavior works through `/api/lawnet/*` routes. - Old route references used by tests/fixtures are updated. - Existing filesystem storage tests still pass. - This refactor can be reviewed and merged independently before the rest of #49.

dernbu referenced this issue

2026-06-14 10:52:51 +02:00

[37.2] PostgreSQL dependency injection for LawNet BFF storage #49

dernbu referenced this issue from a pull request that will close it,

2026-06-14 11:05:51 +02:00

[37.2.1] Rename LawNet BFF API routes under /api/lawnet #54

dernbu closed this issue

2026-06-14 11:10:19 +02:00