Custom Prefix and Suffix Groups
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:
- Support for nested non-capturing groups in regexp, e.g.
/(abc(?=d))
- Support for custom prefix and suffix groups using
/{abc(.*)def}
- Tokens in an unexpected position will throw an error
- Paths like
/test(foo
previously worked treating(
as a literal character, now it expects(
to be closed and is treated as a group - You can escape the character for the previous behavior, e.g.
/test\(foo
- Paths like
Changed
- Revert using any character as prefix, support
prefixes
option to configure this (starts as/.
which acts like every version since 0.x again) - Add support for
{}
to capture prefix/suffix explicitly, enables custom use-cases like/:attr1{-:attr2}?