Skip to content
This repository has been archived by the owner on Jul 19, 2020. It is now read-only.

Allow paths and queries to exist after a fragment #197

Closed
hgzimmerman opened this issue Dec 11, 2019 · 0 comments · Fixed by #211
Closed

Allow paths and queries to exist after a fragment #197

hgzimmerman opened this issue Dec 11, 2019 · 0 comments · Fixed by #211
Labels
breaking change This change will result in a broken build or differing behavior in end-user crates. enhancement New feature or request low priority Other work will take precedence over this. Speed of work may be dependent on external interest.

Comments

@hgzimmerman
Copy link
Member

Description

To better support fragment/hash routing and to make that experience more consistent with the rest of the library, the parser for the routing syntax should recognize paths and queries where possible after a fragment has begun.
This would allow capture groups like {*} and {3} to have a specific meaning in a fragment context if they are used in a path-like position.
@hgzimmerman hgzimmerman added enhancement New feature or request low priority Other work will take precedence over this. Speed of work may be dependent on external interest. breaking change This change will result in a broken build or differing behavior in end-user crates. labels Dec 11, 2019
@hgzimmerman hgzimmerman mentioned this issue Dec 19, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
breaking change This change will result in a broken build or differing behavior in end-user crates. enhancement New feature or request low priority Other work will take precedence over this. Speed of work may be dependent on external interest.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Relax capture rules in Fragment sections in route syntax parser yewstack/yew_router
1 participant
@hgzimmerman