Transformer: URL parsing/regex routing to URLPattern
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- tooling
Research direction
Start by reviewing the existing transformers in src/newlyAvailable/ and their corresponding tests in tests/newlyAvailable/. Implement only high-confidence conversions for URL pathname regex checks and combined host/path checks, then export the transformer from src/newlyAvailable.js. Update README.md with the safe transformation constraints and verify comprehensive tests cover the supported patterns.
Written by the indexing model from the issue text.
Description
Summary
Add a transformer that upgrades common URL regex/parsing routing patterns to URLPattern.
Target transformation
Examples to support where safe:
new URL(u).pathname+ regex.test/.execroute checks ->new URLPattern({ pathname: ... }).test/exec(...)- Manual host/path combination checks -> one
URLPatternwithhostname+pathname.
Scope
- Baseline category: newly available (URLPattern became newly available in Sep 2025).
- Focus only on patterns that can be converted with high confidence.
Acceptance criteria
- Add transformer implementation in
src/newlyAvailable/. - Export from
src/newlyAvailable.js. - Add comprehensive tests in
tests/newlyAvailable/. - Document in
README.mdwith safe transformation constraints.
Sources
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 2
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 28
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codingjoe/esupgrade
-
widely available
Difficulty 3/5 1-2 days Newbie friendliness 72/100
codingjoe/esupgrade#217 · 1 comment ·
Maintainers usually reply within 1 day
-
newly available
Difficulty 3/5 1-2 days Newbie friendliness 66/100
codingjoe/esupgrade#211 · 1 comment ·
Maintainers usually reply within 1 day
-
widely available
Difficulty 3/5 1-2 days Newbie friendliness 72/100
codingjoe/esupgrade#212 · 1 comment ·
Maintainers usually reply within 1 day
-
widely available
Difficulty 3/5 1-2 days Newbie friendliness 68/100
codingjoe/esupgrade#213 · 1 comment ·
Maintainers usually reply within 1 day
-
widely available
Difficulty 3/5 1-2 days Newbie friendliness 69/100
codingjoe/esupgrade#215 · 1 comment ·
Maintainers usually reply within 1 day
All issues in codingjoe/esupgrade
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tshemsedinov/reslop#158 ·
Maintainers usually reply within 1 day
-
level/task type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wazuh/wazuh-documentation#10398 ·
Maintainers usually reply within 1 day
-
app_installations reports an error on every repo or suborg change when the plugin is not configuredOpen
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
github-community-projects/safe-settings#1111 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day