This project has given up GitHub. (See Software Freedom Conservancy's Give Up GitHub site for details.)
You can now find this project at paste.rossabaker.com instead.
Any use of this project's code by GitHub Copilot, past or present, is done without our permission. We do not consent to GitHub's use of this project's code in Copilot.
Join us; you can give up GitHub too! Ready to make the change? Have a look at the convenience script.
We need to be sure that it doesn't conflict with the existing routing syntax. If the closure takes parameters, then that could trigger the by-position mapping -- I think that would work.
Perfect!
:? Does not blur the closure parameter names with request path parameters.
Of course, this way one cannot use params("?") at the same time of passing params to the closure. Nice.
Hope the idea to be useful.
Yes, this is definitely a feature that we would like to add. Thanks for the idea!
I think the param names are less important, since the action will perform some operation over the closure parameters. But the params order yes, can be meaningful. Annotation can be expensive and annoying. Can a simply convetion solve this?
The convention could be option. People would decide to explicit the parameters or grab them using params(..). :)