Expand popular framework route extraction - #234
Merged
Conversation
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
Motivation
Compass already recognized many framework-local registrations, but popular ecosystems still had important gaps: Angular configs, Echo/Fiber routes, Minimal APIs, and cross-module Node router mounts. This change fills that first cross-language slice without adding central framework dispatch branches or allowing one framework adapter to mutate another.
Verification
All commands above pass. The broader pre-existing
cargo clippy -p compass-resolve --all-targetstest lint remains blocked by unrelatedexpect/panicand collapsible-if violations inframework_qualification.rsandpython_import_provenance.rs; the required workspace lib/bin lint passes.Compatibility and documentation
The public graph and CLI schemas are unchanged. Extraction semantics advance from v10 to v11 so cached facts rebuild and expose the new additive route evidence.
docs/reference/framework-routes.mdandCHANGELOG.mddescribe the supported shapes.Checklist
MIT OR Apache-2.0