Proposal: Change URL's signature to match [S]Printf about templ HOT 3 OPEN

I think it would be standard form for that to be an extra function that ends with f such as URLf. I believe that this standard is used by editors to highlight the format string differently.

from templ.

I like the idea of having a url format / builder function.

If it was the signature of Sprintf, e.g.: urlf.Sprintf("/path/%s/fileName.js?%s=%v", "pathvar/", "qkey?", "&other=true") there's a few dangers to consider... Because of the context of the variable substitution, there's a risk of injection attacks, so the values would need to be appropriately escaped:

• path variables need to be path escaped so that / etc. is encoded.
• query variables need to be query escaped so that ?, = etc. are properly encoded.

There's also the question of what happens if you do something like:

urlf.Sprintf("?%s", "data")

It could live in github.com/a-h/templ/urlf to avoid the name of oddity of templ.URLf or similar, but I don't mind templ.URL

I wonder if a builder style is better, since it turns issues with sprintf replacement into compile time issues:

urlbuilder.Build().Path("a").Path("b").Path(c).Query(key, value)

from templ.

There could be an unsafe counterpart too, urlf.UnsafeSprintf.

from templ.