You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: sub-routers and route prefix composition (include_router) #46
Today App is a flat registry: every route is registered on one object. Large APIs need namespaced paths (/api/v1/..., /admin/...) without repeating prefixes on every decorator.
Add something like APIRouter / include_router(router, prefix=..., **defaults) in Python, merging route tables and OpenAPI paths into the parent App before freeze().
Alternatively: a prefix argument on the existing get/post/... decorators only (weaker, but less API surface).
OpenAPI: merged paths must remain valid; duplicate path+method should error at register time.
Acceptance criteria
At least one example under examples/ with two routers and a shared prefix.
Pytest: routes under prefix resolve; OpenAPI lists prefixed paths.
Activity
chore(issues): add v0.3.0 bodies 21-24 and GitHub #46-49
Merge pull request #61 from QueryaHub/issue-46-api-router