Datner

Hi @alicanerdurmaz , You're "looking" in the wrong end here. You're using the existing `Link` that will use some default `Link` implementation, or one provided by the `RouterContext`. So your...

--- I understand that the team don't see this as an issue and are not interested in 'fixing' it as it is not considered broken. This is fine, I accept...

@arekmaz this would be right if we were validating, but we're parsing. And more importantly, multipart forms are designed such that you can take a single one, or get all...

@arekmaz I have no idea what you are basing this on... intuition? rationalization? [the spec for `form-urlencoded`](https://url.spec.whatwg.org/#application/x-www-form-urlencoded) doesn't say this [the api for `form-urlencoded`](https://url.spec.whatwg.org/#interface-urlsearchparams) doesn't say this [the api for...

@arekmaz > the canonical shape should be `string[]` But we're not whatwg, we don't get to decide, and they decided it's a sum type `string | string[]`. > every field...

I don't understand, this is not an issue. We **agree** that this is not an issue. I _showed_ exactly how this behaves. single value ```ts const sp1 = new URLSearchParams([['a',...

I am not sure if it is unique, I'll leave that judgement to others. I do think that there is logic in the methods. Though it's description is incorrect. It...

@mikearnaldi I think you might have accidentally closed this issue despite reverting #3023

Hmm thats not entirely true though, the templating syntax **can** be used as they describe. I don't quite understand the gaslighting 😜 Theres even fancy semantics and highlighting for it...

Oh yeah, totally. I chanced upon this notation in the videos just like you have. Color me surprised. I'm with you, I commented on this: > the templating syntax cannot...