lukeed/polka
### [`v1.0.0-next.22`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.22)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.21...v1.0.0-next.22)
#### Patches
- (`polka`) Ensure `error.status` is numeric before assigning as status code ([#178](https://togithub.com/lukeed/polka/issues/178)): [`8448ac0`](https://togithub.com/lukeed/polka/commit/8448ac0)
*Thank you [@lovasoa](https://togithub.com/lovasoa)*
- (`polka`) Ensure `error.status` is 3-digit status code: [`561558b`](https://togithub.com/lukeed/polka/commit/561558b)
### [`v1.0.0-next.21`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.21)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.20...v1.0.0-next.21)
#### Breaking
- (`polka`) Remove `code` property support for `next()` errors: [`f95a5b4`](https://togithub.com/lukeed/polka/commit/f95a5b4)
*Previously any errors or custom error-objects could use the `code` property to set the response status code. However, this could pose a problem with native `Error` types that set an error code (eg, `"ENOENT"`) which is an invalid status code.*
*Now you must use the `status` property, which was always supported, but took a backseat to `code`'s existence. Express also supports the `status` property.*
```diff
next({
-- code: 422,
++ status: 422,
message: 'Invalid content',
});
```
#### Chores
- (`@polka/url`) Accomodate an updated error message in test expectant: [`d30d448`](https://togithub.com/lukeed/polka/commit/d30d448)
### [`v1.0.0-next.20`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.20)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.19...v1.0.0-next.20)
#### Breaking
- (`@polka/url`): Remove `toDecode` parameter ([#175](https://togithub.com/lukeed/polka/issues/175)): [`e45fe88`](https://togithub.com/lukeed/polka/commit/e45fe88)
*Apparently no one was using it except for me 😆 so I removed it as it was causing cache/mutation conflicts in rare cases downstream.*
### [`v1.0.0-next.19`](https://togithub.com/lukeed/polka/compare/v1.0.0-next.18...v1.0.0-next.19)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.18...v1.0.0-next.19)
### [`v1.0.0-next.18`](https://togithub.com/lukeed/polka/compare/v1.0.0-next.17...v1.0.0-next.18)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.17...v1.0.0-next.18)
### [`v1.0.0-next.17`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.17)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.16...v1.0.0-next.17)
#### Patches
- (`@polka/url`): Ensure `toDecode` value is considered during `req._parsedUrl` cache match: [`f64b4bb`](https://togithub.com/lukeed/polka/commit/f64b4bb)
*For example, if you `parse` a URL without decoding it, that previous result should not be reused if you call `parse` again w/ `toDecode` set to `true` this time. Should be true for the reverse situation too.*
### [`v1.0.0-next.16`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.16)
[Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.15...v1.0.0-next.16)
#### Breaking
- No longer automatically decodes `req.url` and `req.path` values anymore ([#172](https://togithub.com/lukeed/polka/issues/172)): [`6ef32a6`](https://togithub.com/lukeed/polka/commit/6ef32a6), [`363e1f6`](https://togithub.com/lukeed/polka/commit/363e1f6)
*Previously, these properties had already passed through `decodeURIComponent`, which could affect Polka's own routing ([#142](https://togithub.com/lukeed/polka/issues/142)) or external middleware that always expected `req.path` and/or `req.url` to remain percent-encoded.*
*However, **all `req.params` values are still decoded!***
*This change aligns Polka with the default Express decoding behavior.*
#### Chores
- (url): Mention `toDecode` parameter in `@polka/url` README ([#168](https://togithub.com/lukeed/polka/issues/168)): [`363e1f6`](https://togithub.com/lukeed/polka/commit/363e1f6)
Configuration
📅 Schedule: "before 3am on the first day of the month" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, click this checkbox.
This PR contains the following updates:
1.0.0-next.15->1.0.0-next.22Release Notes
lukeed/polka
### [`v1.0.0-next.22`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.22) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.21...v1.0.0-next.22) #### Patches - (`polka`) Ensure `error.status` is numeric before assigning as status code ([#178](https://togithub.com/lukeed/polka/issues/178)): [`8448ac0`](https://togithub.com/lukeed/polka/commit/8448ac0) *Thank you [@lovasoa](https://togithub.com/lovasoa)* - (`polka`) Ensure `error.status` is 3-digit status code: [`561558b`](https://togithub.com/lukeed/polka/commit/561558b) ### [`v1.0.0-next.21`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.21) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.20...v1.0.0-next.21) #### Breaking - (`polka`) Remove `code` property support for `next()` errors: [`f95a5b4`](https://togithub.com/lukeed/polka/commit/f95a5b4) *Previously any errors or custom error-objects could use the `code` property to set the response status code. However, this could pose a problem with native `Error` types that set an error code (eg, `"ENOENT"`) which is an invalid status code.**Now you must use the `status` property, which was always supported, but took a backseat to `code`'s existence. Express also supports the `status` property.* ```diff next({ -- code: 422, ++ status: 422, message: 'Invalid content', }); ``` #### Chores - (`@polka/url`) Accomodate an updated error message in test expectant: [`d30d448`](https://togithub.com/lukeed/polka/commit/d30d448) ### [`v1.0.0-next.20`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.20) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.19...v1.0.0-next.20) #### Breaking - (`@polka/url`): Remove `toDecode` parameter ([#175](https://togithub.com/lukeed/polka/issues/175)): [`e45fe88`](https://togithub.com/lukeed/polka/commit/e45fe88) *Apparently no one was using it except for me 😆 so I removed it as it was causing cache/mutation conflicts in rare cases downstream.* ### [`v1.0.0-next.19`](https://togithub.com/lukeed/polka/compare/v1.0.0-next.18...v1.0.0-next.19) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.18...v1.0.0-next.19) ### [`v1.0.0-next.18`](https://togithub.com/lukeed/polka/compare/v1.0.0-next.17...v1.0.0-next.18) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.17...v1.0.0-next.18) ### [`v1.0.0-next.17`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.17) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.16...v1.0.0-next.17) #### Patches - (`@polka/url`): Ensure `toDecode` value is considered during `req._parsedUrl` cache match: [`f64b4bb`](https://togithub.com/lukeed/polka/commit/f64b4bb) *For example, if you `parse` a URL without decoding it, that previous result should not be reused if you call `parse` again w/ `toDecode` set to `true` this time. Should be true for the reverse situation too.* ### [`v1.0.0-next.16`](https://togithub.com/lukeed/polka/releases/v1.0.0-next.16) [Compare Source](https://togithub.com/lukeed/polka/compare/v1.0.0-next.15...v1.0.0-next.16) #### Breaking - No longer automatically decodes `req.url` and `req.path` values anymore ([#172](https://togithub.com/lukeed/polka/issues/172)): [`6ef32a6`](https://togithub.com/lukeed/polka/commit/6ef32a6), [`363e1f6`](https://togithub.com/lukeed/polka/commit/363e1f6) *Previously, these properties had already passed through `decodeURIComponent`, which could affect Polka's own routing ([#142](https://togithub.com/lukeed/polka/issues/142)) or external middleware that always expected `req.path` and/or `req.url` to remain percent-encoded.* *However, **all `req.params` values are still decoded!*** *This change aligns Polka with the default Express decoding behavior.* #### Chores - (url): Mention `toDecode` parameter in `@polka/url` README ([#168](https://togithub.com/lukeed/polka/issues/168)): [`363e1f6`](https://togithub.com/lukeed/polka/commit/363e1f6)
Configuration
📅 Schedule: "before 3am on the first day of the month" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.