feat: discover SolidStart file pages and endpoints - #11
Open
bompus wants to merge 2 commits into
Open
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
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.
SolidStart 2 default file routes now produce page and method-qualified endpoint nodes linked to their exact local components or handlers. The extractor follows registered default configuration, page-only layout hierarchy, groups and parameters, and GET-to-HEAD fallback; it skips unsupported overrides and dynamic registration.
Validated against pinned 2.0.4 official About and API source fixtures, page/API coexistence, mutation/type/shadowing negatives, scoped and reopened sync, and fresh compiled workers. Build passes; 115 focused WASM/control tests pass; full native suite: 4,542 passed, 46 skipped. Independent review findings were fixed and rechecked.
Stacked on #10; step 9 of the approved framework coverage sequence. Coverage matrix, user guide and changelog include supported syntax and limits.