-
-
Notifications
You must be signed in to change notification settings - Fork 16.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate app.all('/*', fn) #2245
Comments
a whole list of practices we could think of that makes us go "WTF r u doing?" would be nice as error messages i think. can't cite any examples though |
I think this goes down a potentially bad road of tons of random code to catch cases we don't normally care about but with the downside of potentially preventing someone from experimenting with something. |
I'm not sure about @jonathanong 's comment, but the intent of the original issue here is because the new path-to-regexp does not support the trailing |
There's probably one or two valid use cases for |
There is no use-case, unless you want every |
This was a stop-gap idea and is no longer necessary since I have a better way to go about adding deprecation messages to old path syntax. People are free to shoot themselves in the foot using |
This is an idea to deprecate and display a message when someone adds the route
.all('/*', fn)
(part of the preparation for #2173). The*
at the end syntax is going away, and this specific case with.all
is a prime thing to start yelling at people about now in 4.x since it makes no sense. I can't imagine a reason they wouldn't want.use(fn)
, except for mis-understanding.The text was updated successfully, but these errors were encountered: