Complete Axum route extraction and route visualization - #232
Merged
Conversation
…oute-extraction # Conflicts: # CHANGELOG.md # crates/compass-output/assets/viewer/graph.js # crates/compass-output/assets/viewer/manifest.json # packages/compass-viewer/src/workbench/VisualizationWorkbench.test.tsx
forhappy
marked this pull request as ready for review
August 13, 2026 06:10
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.
Summary
nest/mergechains, uniquely resolved cross-module factory calls, and direct factory returnslayer/route_layermiddleware with import-aware targetsRoot cause
Axum extraction previously understood only routes and prefixes visible in one inline builder expression. Router ownership was lost when a child router moved through a local variable or module factory, so nested prefixes and middleware never reached its routes. The workbench then forced every artifact lens onto the square grid and displayed terminal handler names, making distinct
handler()targets overlap.Impact
A clean qualification run against EpicGames/lore now publishes the production health, repository-content, presigned, authentication, and tracing flow. Its route lens increased from the four relationships in the reported export to 19 exact route relationships, with complete composed URLs and distinct handler labels.
Dynamic paths or runtime-selected factories remain unresolved; ambiguous and recursive structural compositions intentionally remain local rather than being guessed.
Validation
cargo fmt --all -- --checkcargo clippy --workspace --lib --bins --locked -- -D warningscargo test --workspace --lib --bins --lockedcargo test -p compass-resolve --test native_routes --lockedcargo test -p compass-output lenses --lockednpm run typecheck:jsnpm run test:js(184 viewer, 120 VS Code, and 80 browser tests)node scripts/check_viewer_assets.mjs./scripts/qualify_code_graph_v1.sh --fixtures-only(27 flows, 24 negatives, deterministic clean/warm/rebuild/alternate-checkout equality)