feat: discover Qwik City pages and endpoints - #12
Open
bompus wants to merge 3 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.
Qwik City default index pages and method-specific exports now produce routes linked to their exact components and handlers. Anonymous default
component$expressions receive a component symbol; named and anonymous factory components retain their callback calls. Layouts and generic middleware do not become endpoints.Validated against pinned 1.20.0 official page/API source fixtures, parameters/groups, page/API coexistence, config and export negatives, scoped/reopened sync, and fresh compiled workers. Build passes; 112 WASM focused/control tests pass; full native suite: 4,562 passed, 46 skipped. Independent review found a named-factory call-chain gap, fixed and rechecked.
Stacked on #11; step 10 of the approved framework coverage sequence. Coverage matrix, user guide and changelog state supported syntax and limits.