parse fastify routes#986
Merged
Merged
Conversation
5a68475 to
e56319c
Compare
e56319c to
12d1396
Compare
11 tasks
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.
Context
Fastify was still extracted by a receiver-name line scanner. It missed multiline and
.route(...)registrations, accepted unrelatedserver.getcalls, and could not prove receiver ownership or safe handler edges.What Changed
.route({ method, url, handler })objects with duplicate/dynamic property rejection.require("fastify")aliases and destructuredfastifyaliases are supported without promoting mutable alias-member factories.How To Review
Review
framework_routes.rsin order: query/object extraction, malformed fallback, query/binding ownership, transparent wrappers and write invalidation, then the Fastify regression matrix. Inlib.rs, confirm Fastify alone moved to the parser adapter and handler reconciliation remains conservative.Verification
fidelity_regression: 8/8.tictactoe_language_coverage: 12/12.cargo clippy -p codestory-indexer -p codestory-runtime --all-targets -- -D warnings.cargo fmt --all -- --check.git diff --check origin/dev/codestory-next...HEAD.12d13962ondev/codestory-next30064e9f; focused Fastify and runtime coverage tests rerun after the final fetch.CODESTORY_REAL_REPO_DRILL_CASESwas unset and nobge-base-en-v1.5.Q8_0.ggufmodel directory existed. No stats success is claimed.Risk
Fastify plugin-prefix propagation and runtime middleware/schema semantics remain out of scope, so confidence stays heuristic despite parser-backed provenance. Malformed recovery remains structural only. No dependency or generic framework abstraction was added.
Closes #979
Refs #920
Refs #899