feat(routing): discover static routes across HTTP frameworks - #2
Open
bompus wants to merge 2 commits into
Open
Conversation
bompus
marked this pull request as ready for review
September 7, 2026 04:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CodeGraph now discovers literal HTTP routes in Hono, Elysia, Fastify, Hyper-Express, Koa router, H3, Bun, Effect v4 and option-free Vixeny builders. An imported handler in
new Hono().get('/users', handler)becomesGET /userslinked to that handler; inline handlers contribute their direct calls, and static responses get endpoints without invented handler links.Nuxt's default file routes now handle root index pages, Nuxt 4 route groups,
server/routes/, server method suffixes and catch-all paths. Server default exports and standard event-handler wrappers link to their handlers. Existing Next Pages/App Router and Vue navigation behavior is retained.The reader uses the existing tree-sitter parser and follows package imports, immutable local router bindings and supported same-file prefixes/mounts. Computed paths, spread configuration, cross-file mounts, runtime mutation and plugin factories are outside coverage. Vixeny options, Nuxt custom configuration and member-handler resolution remain unsupported. Re-index existing projects after upgrading; no new dependencies or application execution.
Validation:
Start review with
src/resolution/frameworks/http-routing.tsand its tests. The route guide documents supported shapes;docs/design/framework-coverage.mdlinks the exact official fixtures and records their limits.