Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
cleaning up README, adding CHANGELOG
- Loading branch information
1 parent
53801a2
commit a6a4a29
Showing
2 changed files
with
40 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
## 4.1.0 | ||
- adds `parsedMethods` option to specify which request methods will be parsed | ||
- deprecates `strict` option, which will be removed in koa-body 5.0.0 | ||
|
||
### Migrating from 4.x.x to 4.1.0 | ||
Migration from prior 4.x.x versions is strightforward. | ||
|
||
- If you used `strict: true`, simply remove this option. The new defaults will behave the same way. | ||
- If you used `strict: false`, set `parsedMethods` to the set of methods you would like to parse. For example, `parsedMethods: ['GET', 'POST', 'PUT', 'PATCH']` | ||
|
||
## 4.0.0 - 4.0.8 - Summary of Changes | ||
- mutliple type definition updates | ||
- adds `includeUnparsed` option to get raw body | ||
|
||
## Breaking Changes in v3/4 | ||
To address a potential [security vulnerability](https://snyk.io/vuln/npm:koa-body:20180127): | ||
- The `files` property has been moved to `ctx.request.files`. In prior versions, `files` was a property of `ctx.request.body`. | ||
- The `fields` property is flatten (merged) into `ctx.request.body`. In prior versions, `fields` was a property of `ctx.request.body`. | ||
|
||
If you do not use multipart uploads, no changes to your code need to be made. | ||
|
||
Versions 1 and 2 of `koa-body` are deprecated and replaced with versions 3 and 4, respectively. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters