Skip to content

Releases: ibraheemdev/matchit

0.9.1

26 Dec 21:07

Choose a tag to compare

  • Fixed inconsistencies around routes without leading slash (#82, #84).
  • Fixed insertion of overlapping route with suffix (#83).

0.9.0

26 Oct 21:34

Choose a tag to compare

  • Fixed a bug that caused empty routes to be ignored on insert (#76).
  • Tightened the rules around overlapping parameter prefixes and suffixes, where ambiguous routes were inadvertently allowed (#67). See the new conflict rules for details.

0.8.6

02 Jan 22:50

Choose a tag to compare

  • Added support for parameter suffixes, e.g. /{name}.png (#17).
  • Performance improvements.

0.8.5

07 Nov 23:10

Choose a tag to compare

  • Added Params::{default, new} (#63).
  • Added Router::merge to combine two routers (#62).
  • Fixed a bug where empty route parameters were accepted (#60).

0.8.4

07 Nov 23:08

Choose a tag to compare

  • Minor performance improvements.

0.8.3

30 Jun 21:32

Choose a tag to compare

  • Implemented ExactSizeIterator for ParamsIter (#54)

0.8.2

28 Apr 19:23

Choose a tag to compare

  • Add Router::remove.

0.8.1

28 Apr 19:22

Choose a tag to compare

  • Implement Debug for Router.

0.8.0

10 Mar 21:50

Choose a tag to compare

This a large release containing a number of new features and breaking changes.

  • The syntax for route parameters has been changed. Named parameters are now marked by {x} and catch-all parameters with {*x}. This allows for more flexibility and support for more complex routes in the future.
  • The { and } characters can be escaped with {{ and }} in static routes.
  • Trailing slash redirect support has been removed. Routes like /foo and /foo/ are now treated as completely disconnected. To achieve redirect behavior, routes must be registered twice, with and without a trailing slash.
  • Catch-all parameters without a leading slash are now supported (#42).

0.7.3

22 Sep 02:28

Choose a tag to compare

  • Better support for overlapping route parameters. The name of a route parameter no longer has any affect on conflicts, meaning routes like /user/:filter/search and /user/:id no longer overlap. (#13).