Looking at the explainer it appears to use custom pattern matching for the url_handlers origins and web_apps paths. Rather than create a new one-off pattern matcher, it would be nice to re-use the primitive we are building in https://github.com/WICG/urlpattern. Its initially being integrated into service workers, but we plan to bring it to manifest scope and other web APIs as well.
The design doc has a lot more detail on the pattern API.
I'm actively implementing URLPattern now and plan to have it in testable shape behind a flag in Q4.
I'd be happy to work with you to figure out how best to integrate it into pwa-url-handler. Also, if it doesn't meet your use cases for some reasons it would also be great to have that feedback. Thanks.
Looking at the explainer it appears to use custom pattern matching for the url_handlers origins and web_apps paths. Rather than create a new one-off pattern matcher, it would be nice to re-use the primitive we are building in https://github.com/WICG/urlpattern. Its initially being integrated into service workers, but we plan to bring it to manifest scope and other web APIs as well.
For more info see:
The design doc has a lot more detail on the pattern API.
I'm actively implementing URLPattern now and plan to have it in testable shape behind a flag in Q4.
I'd be happy to work with you to figure out how best to integrate it into pwa-url-handler. Also, if it doesn't meet your use cases for some reasons it would also be great to have that feedback. Thanks.