Closed frank-dspeed closed 2 years ago
This not a regression or a bug, the documentation is in the README. If you want the literal translation between old and new formats it's /files/:file(.*)
and (.*)
(*
basically means .*
in 0.1.x), feel free to open a PR to add them to the compatibility docs if you think it'd help others!
@blakeembrey sorry that i ping you again but i tested it and i still get
pathToRegexp get called with {
path: '.*',
opts: { sensitive: undefined, strict: undefined, end: true },
keys: []
}
TypeError: Unexpected MODIFIER at 1, expected END
maybe i need to explicit do /(.*)
?
Ok i got it all works nice thanks a lot for the good documentation do you know any reason for express to not take the new syntax?
for express to not take the new syntax?
The current express router is still based on the old version, when it upgrades it'll get the new syntax (in express 5).
i copy the details from my issue that i got after upgrading from 0.1.7
Details First Error
Details Secund Error
i hope some one in here can tell me the migration path i think already the first issue is solved when i replace
but i am not sure about the secund case i need clarification the input parameters and expected and current output are there
my first observation for the first issue is also that it produces the same regex but missing the i at the end i found
but i am still not sure how to fix that i can rewrite the one failing test and i can correct the example and docs to not use only the * but i need clear replacements i am not sure if i got everything right