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
When a required path variable is not provided the router leaves the token in the generated url.
Say I have a route with the uri /page/{id}/edit. If I pass an empty params argument the generated uri will be /page/{id}/edit.
I think it is more helpful to detect the missing parameter and raise an error.
I see two options:
1/ Compile the routes server side and add the variables in the exported content
2/ Write JS code that compiles the route (maybe not a complete compilation as it is done server side, but extract enough information for this use case).
The text was updated successfully, but these errors were encountered:
When a required path variable is not provided the router leaves the token in the generated url.
Say I have a route with the uri /page/{id}/edit. If I pass an empty params argument the generated uri will be /page/{id}/edit.
I think it is more helpful to detect the missing parameter and raise an error.
I see two options:
1/ Compile the routes server side and add the variables in the exported content
2/ Write JS code that compiles the route (maybe not a complete compilation as it is done server side, but extract enough information for this use case).
The text was updated successfully, but these errors were encountered: