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: Add wildcard '*' support. #27679

Merged
merged 1 commit into from Feb 24, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Feb 18, 2021

This CL adds support for a wildcard * character in patterns. It is
treated as being equivalent to the (.*) unnamed regexp group. This
means it can have its own following modifiers like *? which can affect
how prefix characters are treated. For example, /foo/*? will match
/foo but /foo/* will not.

This CL deviates from the current upstream path-to-regexp v6.2.0, but
we plan to upstream this change. Initial discussions suggest that its
possible this will be accepted.

Bug: 1141510
Change-Id: I386b03e8bb05aab9586464986faf002e824e189e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2673887
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856942}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2673887 branch 3 times, most recently from 90978eb to b9e8f69 Compare February 23, 2021 20:48
This CL adds support for a wildcard `*` character in patterns.  It is
treated as being equivalent to the `(.*)` unnamed regexp group.  This
means it can have its own following modifiers like `*?` which can affect
how prefix characters are treated.  For example, `/foo/*?` will match
`/foo` but `/foo/*` will not.

This CL deviates from the current upstream path-to-regexp v6.2.0, but
we plan to upstream this change.  Initial discussions suggest that its
possible this will be accepted.

Bug: 1141510
Change-Id: I386b03e8bb05aab9586464986faf002e824e189e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2673887
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856942}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants