rust-urlpattern

rust-urlpattern copied to clipboard

fix: get codepoint range rather than bytes

1

This addresses the panic mentioned here: https://github.com/denoland/deno/issues/20906 https://github.com/denoland/rust-urlpattern/issues/46 I don't know if some additional tests might be warranted here?

melbourne2991

Adding this issue as a repo-local reference for https://github.com/denoland/deno/issues/20906 The issue occurs because we use a range over bytes instead of codepoints which causes a panic.

melbourne2991

fix: make `URLPatternComponentResult::groups` values optional

1

for WICG/urlpattern#162

crowlKats

feat: hasRegExpGroups

1

Implements #42

crowlKats

Implements whatwg/urlpattern#198, for denoland/deno#21073.

crowlKats

whatwg/urlpattern#199 adds a read-only `hasRegExpGroups` property. When/if it's merged, deno may wish to support it as well.

jeremyroman

feat: support for case-insensitive matches

2

Implements WICG/urlpattern#168 Seems there are no WPTs yet

crowlKats

Hi, This PR changes the type of the delimiter associated with the parser options and resolves the following TODO: https://github.com/denoland/rust-urlpattern/blob/e65cfc958000744c5127a4450b48d65bf3e7c129/src/parser.rs#L27

woxtu

Fix `URLPatternResult#inputs` behaviour

1

There is an inconsistency between spec and tests and Chromium. Needs a spec decision https://github.com/WICG/urlpattern/issues/133.

lucacasonato

As described in https://github.com/WICG/urlpattern/issues/61 Available experimentally in Chrome with flag Deno should also have an implementation available with `--unstable` https://wpt.fyi/results/urlpattern?label=master&label=experimental&product=chrome&product=deno&aligned

ghost