undefined | Better HN

0 pointsevilthrow3y ago0 comments

GET /{username}

0 comments

You definitely don't need a framework to get the user name out of a URL, you need one line of code.

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.

morelisp3y ago

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.

telesoft3y ago

Assuming the url is formatted correctly:

  strings.Split(urlString, "user/")[1]

https://go.dev/play/p/tWi-Ge0CA1X

That's one way to do it.

>more URL parameters

I thought thats what http.Request.ParseForm() was for (assuming correct formatting)

morelisp3y ago

> Assuming the url is formatted correctly

... is like, a core job of an HTTP router? You're not just begging the question, you're beating someone up and rifling through their pockets for it.

j / k navigate · click thread line to collapse

0 comments

telesoft3y ago

You definitely don't need a framework to get the user name out of a URL, you need one line of code.

evilthrowOP3y ago

morelisp3y ago

telesoft3y ago

Assuming the url is formatted correctly:

  strings.Split(urlString, "user/")[1]

https://go.dev/play/p/tWi-Ge0CA1X

That's one way to do it.

>more URL parameters

I thought thats what http.Request.ParseForm() was for (assuming correct formatting)

morelisp3y ago

> Assuming the url is formatted correctly

... is like, a core job of an HTTP router? You're not just begging the question, you're beating someone up and rifling through their pockets for it.

j / k navigate · click thread line to collapse