erikringsmuth/app-router

regular expression + data binding

Open

#27 opened on Oct 1, 2014

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (83 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (608 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I think app-router could use regular expressions in order to match path variables. Regex with named captures would be great but Javascript doesn't support them natively (xregexp is a js library that support named captures). Even simple native capture groups (by index number) would be great.

An example:

<!-- url -->
http://www.example.com/demo/15

<!-- route, notice variables attribute  -->
<!-- first capure [word (\w+)], second capture [number (\d+)] -->
<app-route path="/^\/(\w+)\/(\d+)$/i" regex variables="word number" import="/pages/regex-page.html"></app-route>

<!-- data binding -->
<regex-page word="demo" number="15"></order-page>

It's much more powerful than actual path variable data binding (using semicollon like :pathArg1). Thank you for app-router.

Contributor guide

Research direction
Examine the current route matching logic in app router. Understand how path variables with colon syntax work. Then implement regex support by parsing the path attribute as a regex pattern and extracting capture groups. Consider using JavaScript's RegExp object. The example shows variables attribute mapping capture groups to names. Ensure backward compatibility. Write tests for various regex patterns.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65