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
If you do /route/match* , and then navigate to /route/match/ or /route/match you get an error in both cases. So, you need to double up with:
/route/match /route/match/*
And this creates discrepancy between express and choo methodology which is visible especially when passing routes down to choo from express level to accomplish SSR.
The text was updated successfully, but these errors were encountered:
graforlock
changed the title
Support express style routing
Support express style routing with trailing wildcard
Sep 14, 2017
Expected behavior
/route/match*
is a standard behavior.Actual behavior
/route/match*
breaks the router.Steps to reproduce behavior
If you do
/route/match*
, and then navigate to/route/match/
or/route/match
you get an error in both cases. So, you need to double up with:/route/match
/route/match/*
And this creates discrepancy between
express
andchoo
methodology which is visible especially when passing routes down tochoo
fromexpress
level to accomplish SSR.The text was updated successfully, but these errors were encountered: