Ben Kelly
Ben Kelly
Well, I think a single param match can kind of be written like this: `new URLPattern({ search: '{*&}?q=foo{&*}?' })` But I admit its ugly. I'm not saying what URLPattern offers...
Seems like yes we should include it.
Basically it would be a convenience to call `test()` or `exec()` only once. Also, there might be some future use where we could provide some default sorting for sites that...
After further thought I'm going to postpone working on URLPatternList. I have limited bandwidth and want to focus on getting URLPattern out the door. Since the list offers limited value...
Note, I opened a separate issue (#61) for ordering of URLPattern objects.
Developers have pointed out that popular routing systems offer optimized route lookup using data structures like radix trees, etc. For example, see [find-my-way](https://github.com/delvedor/find-my-way). This allows them to find the "best"...
It would be useful to know how devs feel about these possible features: * Ability to associate extra data with a pattern in the list that you can access on...
I don't think we will have to iterate all entries in the list. At a minimum we can always at least optimize "prefix match" patterns that begin with fixed text....
> What is critical to me, as a consumer of the API to build client side routing, is supporting repeatable params. Can you tell me more about repeatable params? Is...
Oh. Parameters with a repeating modifier. Got it. Yes, that is supported in patterns today and will be supported by any container. I was afraid you were asking for something...