url-pattern
Advanced tools
Comparing version 1.0.2 to 1.0.3
@@ -8,3 +8,3 @@ interface UrlPatternOptions { | ||
optionalSegmentEndChar?: string; | ||
wildcardChar: string; | ||
wildcardChar?: string; | ||
} | ||
@@ -11,0 +11,0 @@ |
{ | ||
"name": "url-pattern", | ||
"version": "1.0.2", | ||
"version": "1.0.3", | ||
"description": "easier than regex string matching patterns for urls and other strings. turn strings into data or data into strings.", | ||
@@ -5,0 +5,0 @@ "keywords": [ |
@@ -99,3 +99,3 @@ # url-pattern | ||
### make pattern from string | ||
## make pattern from string | ||
@@ -110,3 +110,3 @@ ```javascript | ||
### match pattern against string | ||
## match pattern against string | ||
@@ -129,3 +129,3 @@ match returns the extracted segments: | ||
### named segments | ||
## named segments | ||
@@ -152,3 +152,3 @@ `:id` (in the example above) is a named segment: | ||
### optional segments, wildcards and escaping | ||
## optional segments, wildcards and escaping | ||
@@ -192,3 +192,3 @@ to make part of a pattern optional just wrap it in `(` and `)`: | ||
### make pattern from regex | ||
## make pattern from regex | ||
@@ -229,3 +229,3 @@ ```javascript | ||
### stringify patterns | ||
## stringify patterns | ||
@@ -263,3 +263,3 @@ ```javascript | ||
### customize the pattern syntax | ||
## customize the pattern syntax | ||
@@ -332,5 +332,5 @@ finally we can completely change pattern-parsing and regex-compilation to suit our needs: | ||
### frequently asked questions | ||
## frequently asked questions | ||
#### how do i match the query part of an URL ? | ||
### how do i match the query part of an URL ? | ||
@@ -350,3 +350,3 @@ the query part of an URL has very different semantics than the rest. | ||
#### how do i match an IP ? | ||
### how do i match an IP ? | ||
@@ -358,4 +358,4 @@ you can't exactly match IPs with url-pattern so you have to | ||
### [contributing](contributing.md) | ||
## [contributing](contributing.md) | ||
### [license: MIT](LICENSE) | ||
## [license: MIT](LICENSE) |
86387