Turn a path string such as `/user/:name` into a regular expression
No API changes. Documentation only release.
Changed
https://github.com/pillarjs/path-to-regexp/compare/v6.2.1...v6.2.2
Added
https://github.com/pillarjs/path-to-regexp/compare/v0.1.7...v0.1.8
Fixed
:name*
parameter (#261) 762bc6bAdded
https://github.com/pillarjs/path-to-regexp/compare/v6.2.0...v6.2.1
Added
Fixed
strict
flag documentation (#227)Fixed
/#?
as default delimiter to avoid matching on query or fragment parameters
delimiter: '.'
Note: The path syntax has been stabilized with this release, no breaking changes in paths is expected.
This release reverts the prefix behavior added in v3 back to the behavior seen in v2. For the most part, path matching is backward compatible with v2 with these enhancements:
/(abc(?=d))
/{abc(.*)def}
/test(foo
previously worked treating (
as a literal character, now it expects (
to be closed and is treated as a group/test\(foo
Changed
prefixes
option to configure this (starts as /.
which acts like every version since 0.x again){}
to capture prefix/suffix explicitly, enables custom use-cases like /:attr1{-:attr2}?
No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.
Changed
RegexpOptions
interface to TokensToRegexpOptions
normalizePathname
from library, document solution in READMEencodeURIComponent
Removed
whitelist
in favor of decodeURI
(advanced behavior can happen outside path-to-regexp
)Fixed
String.prototype.normalize
to continue supporting IEAdded
/%.-
)