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 }}
Repository navigation
[Feature ✨]: Support tagged template literals for multiple paths #127
With the introduction of having multiple paths for one route, it might be useful to have a way to have an option in an arbitrary place in a path eg. using tagged template literals like so:
Maybe it would make more sense to use some special pattern for this?
Maybe '/example/(foo|bar)/thing?'.
Another option:
<Route path="/example/:name/thing?" allowedParams={{ name: ['foo', 'bar'] }} />
Activity
orenelbaum commentedon Dec 7, 2022
Maybe it would make more sense to use some special pattern for this?
Maybe
'/example/(foo|bar)/thing?'.Another option:
<Route path="/example/:name/thing?" allowedParams={{ name: ['foo', 'bar'] }} />
JorrenH commentedon Jan 20, 2023
@orenelbaum your last suggestion is now possible with #227 using the following:
fabiospampinato commentedon Mar 12, 2023
/example/(foo|bar)/thing?would be a valid Express path by the way, if the router switched to that this would work out of the box.