Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URLPattern #9

Closed
wanderview opened this issue Oct 9, 2020 · 4 comments
Closed

URLPattern #9

wanderview opened this issue Oct 9, 2020 · 4 comments

Comments

@wanderview
Copy link

Introduction

Service workers scopes currently use a very simplistic URL matching mechanism. We have heard from a number of sites that scopes could benefit from a more expressive pattern syntax. In addition, web developers often need to match URLs in order to implement routing systems.

This proposal introduces a URL matching primitive that can be used both directly in javascript and in web platform APIs like service workers.

Read the complete Explainer.

This proposal has been reviewed by the TAG.

There is also a detailed design doc that goes into greater API and chromium implementation details.

This proposal was discussed at TPAC 2019 and a virtual call around TPAC 2020.

The group decided at the latest meeting URLPattern should be spec'd under WICG to start. I'd like to move the explainer repo to WICG and rename it to urlpattern. Eventually the service worker bits will move out to the service worker WG repo.

Feedback (Choose One)

I welcome feedback in this thread, but encourage you to file bugs against the Explainer.

@asakusuma
Copy link

LinkedIn is very interested in being able to handle routing across different JS environments using the same built in primitives.

@yoavweiss
Copy link
Collaborator

Sounds like we have enough support to move over the repo!

@wanderview
Copy link
Author

The repo has been moved to:

https://github.com/wicg/urlpattern

Thanks @yoavweiss!

Not sure if this issue stays open or should be closed.

@yoavweiss
Copy link
Collaborator

Added a label indicating the repo was adopted. I think we can leave it open, use labels to keep track of progress until it's migrated to a WG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants