Skip to content

Commit

Permalink
docs: linting
Browse files Browse the repository at this point in the history
  • Loading branch information
UlisesGascon committed Oct 9, 2024
1 parent 5759126 commit 1712f98
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions _posts/2024-09-12-v5-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,7 @@ We recognize that this might cause difficulty for some enterprises with older or

### Path matching and regular expressions

The v5 releases updates to `[email protected]` from `[email protected]`, which incorporates many years of changes. If you were using any of the 5.0.0-beta releases, a last-minute update which greatly changed the path semantics to [remove the possibility of any ReDoS attacks](https://blakeembrey.com/posts/2024-09-web-redos/). For
more detailed changes, [see the `path-to-regexp` readme](https://github.com/pillarjs/path-to-regexp?tab=readme-ov-file#express--4x).
The v5 releases updates to `[email protected]` from `[email protected]`, which incorporates many years of changes. If you were using any of the 5.0.0-beta releases, a last-minute update which greatly changed the path semantics to [remove the possibility of any ReDoS attacks](https://blakeembrey.com/posts/2024-09-web-redos/). For more detailed changes, [see the `path-to-regexp` readme](https://github.com/pillarjs/path-to-regexp?tab=readme-ov-file#express--4x).

#### 1. No more regex

Expand All @@ -45,12 +44,10 @@ This is a commonly-used pattern, but we removed it for security reasons. Unfortu

This release includes simplified patterns for common route patterns. With the removal of regular expression semantics comes other small but impactful changes to how you write your routes.

1. `:name?` becomes `{:name}`. Usage of `{}` for optional parts of your route means you can now do things like `/base{/:optional}/:required` and what parts are actually optional is
much more explicit.
1. `:name?` becomes `{:name}`. Usage of `{}` for optional parts of your route means you can now do things like `/base{/:optional}/:required` and what parts are actually optional is much more explicit.
2. `*` becomes `*name`.
3. New reserved characters: `(`, `)`, `[`, `]`, `?`, `+`, & `!`. These have been reserved to leave room for future improvements and to prevent mistakes when migrating where those characters mean specific things in previous versions.


#### 3. Name everything

This release no longer supports ordered numerical parameters.
Expand Down

0 comments on commit 1712f98

Please sign in to comment.