However, if the user enters text with one or more asterisks (*), this throws an error You are trying to access a wild card parameter at index 0 but the value of params at that index is undefined. The same happens with pathFor and urlFor, as reported in #708. The workaround I've found is the following:
But this still limits the number of asterisks the user can enter to 10. Fine for now, but feels like a bug (and it's been annoying to work around it every time I use pathFor and urlFor). It seems that *s should only be interpreted in the route specification, not in the arguments... or maybe I don't understand what wildcards are for.
I have a regular route (no wildcards), and a form submission that triggers a
Router.go
, like so:However, if the user enters text with one or more asterisks (
*
), this throws an errorYou are trying to access a wild card parameter at index 0 but the value of params at that index is undefined
. The same happens withpathFor
andurlFor
, as reported in #708. The workaround I've found is the following:But this still limits the number of asterisks the user can enter to 10. Fine for now, but feels like a bug (and it's been annoying to work around it every time I use
pathFor
andurlFor
). It seems that*
s should only be interpreted in the route specification, not in the arguments... or maybe I don't understand what wildcards are for.