Skip to content

feat: make API route prefix configurable with go-api fallback#7

Merged
seakee merged 2 commits into
mainfrom
feat/config-route-prefix
Mar 18, 2026
Merged

feat: make API route prefix configurable with go-api fallback#7
seakee merged 2 commits into
mainfrom
feat/config-route-prefix

Conversation

@seakee
Copy link
Copy Markdown
Owner

@seakee seakee commented Mar 18, 2026

Summary

  • add system.route_prefix to the runtime config model
  • expose the route prefix in the shipped config templates
  • load the root API route group from config instead of hard-coding go-api
  • keep backward compatibility by falling back to go-api when the config value is empty or missing

Testing

  • go test ./... fails because the repository vendor directory is out of sync with go.mod
  • go test -mod=mod ./... passes for the changed packages, but the repo still has existing failures in command/codegen/codegen
  • existing failures are unrelated to this PR and include a missing bin/data/sql/auth_app.sql fixture plus pre-existing generator assertion failures

seakee added 2 commits March 18, 2026 19:22
Add system.route_prefix to the runtime configuration model and expose it in the shipped environment templates.

This keeps configuration explicit for new deployments while remaining compatible with existing setups that rely on the default go-api prefix.
Replace the hard-coded root API group with a value read from the runtime configuration.

When the route prefix is missing or empty, registration still falls back to go-api so existing environments keep working without changes.
@seakee seakee merged commit 57544c6 into main Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant