Map React Router frontend features#4
Open
moritzscheele wants to merge 2 commits into
Open
Conversation
Add deterministic React mapping for packages with React dependencies, including nested frontend packages, React Router routes, and component slices.
Extend Python mapping with deterministic FastAPI route discovery, include_router prefix handling, docs, and regression coverage.
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
1 participant
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
<Route path element>declarations to their rendered local componentssrc/pagesandsrc/componentsas UI-flow slicesfrontend/,client/,web/, andui/Why
Running Clawpatch from a repository root that contains a nested Vite/React frontend currently misses that frontend unless it is modeled as a workspace. Even when pointed directly at the frontend package, the mapper mostly sees package/config surfaces instead of the user-facing routes and components that need review.
This adds first-party mapper support so React frontends are represented as reviewable feature records without repo-local adapter scripts.
Validation
npx --yes pnpm@11.1.2 typechecknpx --yes pnpm@11.1.2 lintnpx --yes pnpm@11.1.2 testnpx --yes pnpm@11.1.2 format:checknpx --yes pnpm@11.1.2 buildfrontend/package to React route/component featuresUpdate: FastAPI support
This branch now also maps FastAPI
@app/@routerroutes, including commoninclude_router(..., prefix=...)wiring. I validated it against a real repo with a FastAPI backend and nested React frontend: the built CLI mapped 61 FastAPI route features in that backend, alongside the existing Python source groups.