You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 19, 2020. It is now read-only.
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.
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.