Update dependency path-to-regexp to v6 #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.7.0->^6.0.0Release Notes
pillarjs/path-to-regexp
v6.1.0Compare Source
Fixed
/#?as default delimiter to avoid matching on query or fragment parametersdelimiter: '.'v6.0.0Compare Source
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(foopreviously would worked, now it expects(to be closed/test\(fooChanged
prefixesoption 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}?v5.0.0Compare Source
No changes to path rules since 3.x, except support for nested RegEx parts in 4.x.
Changed
RegexpOptionsinterface toTokensToRegexpOptionsnormalizePathnamefrom library, document solution in READMEencodeURIComponentv4.0.5Compare Source
Removed
whitelistin favor ofdecodeURI(advanced behavior can happen outsidepath-to-regexp)v4.0.4Compare Source
Fixed
String.prototype.normalizeto continue supporting IEv4.0.3Compare Source
Added
/%.-)v4.0.2Compare Source
Fixed
RegexpOptionsinmatch(...)functionv4.0.1Compare Source
Fixed
regexpspelling across 4.xv4.0.0Compare Source
All path rules are backward compatible with 3.x, except for nested
()and other RegEx special characters that were previously ignored.Changed
matchdoes not default todecodeURIComponentAdded
normalizePathnameutility for supporting unicode paths in librariesv3.2.0Compare Source
Added
matchfunction to libraryv3.1.0Compare Source
sensitiveoption fortokensToFunction(#191)validateoption to path functions (#178)v3.0.0Compare Source
/:att1-:att2-:att3-:att4-:att5)partialsupport, prefer escaping the prefix delimiter explicitly (e.g.\\/(apple-)?icon-:res(\\d+).png)v2.4.0Compare Source
startoption to disable anchoring from beginning of the stringv2.3.0Compare Source
delimiterwhen processing repeated matching groups (e.g.foo/barhas no prefix, but has a delimiter)v2.2.1Compare Source
end: falseto match both relative and absolute pathsv2.2.0Compare Source
tokenas second argument toencodeoption (e.g.encode(value, token))v2.1.0Compare Source
/foo/before required either/foo/or/foo//to match in non-ending modev2.0.0Compare Source
endsWithto match paths like/test?query=stringup to the query stringdelimitersfor specific characters to be treated as parameter prefixes (e.g./:test)isarraydependency/test/is now treated as/test/instead of/testwhen matching)keysargument that acceptedoptionskeyslist attached to theRegExpoutputtokensToFunction(e.g.compile) to accept anencodefunction for pretty encoding (e.g. pass your own implementation)Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.