Callers can now hit /api/v1/views/table/personne instead of /table/609 and the bridge resolves the slug to the numeric Baserow table ID using the BASEROW_TABLE_IDS env var (already present, just unused before). Resolution accepts either a digits-only string (preserved behavior) or a slug. Falls back to a 400 validation error when neither matches. Note: this fixes the *routing* layer only. The downstream Baserow API still requires a user JWT for some operations (notably GET /views/table) and returns 401 PERMISSION_DENIED with the current DB-token-based bridge config. That's a separate architectural concern — tracked for a later patch (bridge user-JWT exchange). Patch 029. |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| .env.example | ||
| .gitignore | ||
| biome.json | ||
| Dockerfile | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
| vitest.config.ts | ||