And what would that line of code be? As far as I am aware you have to parse the URL string, and it only gets more complicated when you add more URL parameters. Which definitely leads to boilerplate code shared across projects.
It's also not especially performant to do the naive (i.e. short) implementation like this, since you'll likely end up parsing/processing path elements left-to-right rather than in whatever order makes the most sense for your loading.
evilthrow|3 years ago
morelisp|3 years ago
telesoft|3 years ago
That's one way to do it.
>more URL parameters
I thought thats what http.Request.ParseForm() was for (assuming correct formatting)