Breaking (#50), more features and options

3.0.0 (2016-09-12)

For commiting please use npm run commit script.

Starting from this release all the build/pull request/commit chain is changed to follow totally semver, semantic-version and standard-version. Contributing guide is update too, please read it before do anything.

The README.md and CHANGELOG.md files are autogenerated files, so please DO NOT edit them manually - there are tools for that. Readme generation is handled by verb and verb-generate-readme generator, the change log and releasing is handled by standard-version and Git Hooks to follow SemVer more strictly.

The commit message convention is based on Angular's using conventional-changelog which works behind the standard-version. Please follow them while sumbimtting Pull Requests and Bug Reports. If anything is not clear enough in the CONTRIBUTING.md, please open an issue to discuss it and propably change it.

Advanced npm scripts is used to handled any linting and errors. So you won't be able to even push anything if simply running npm test fails. Everything is totally coupled and there's zero chance to do something wrong. From now on, project will follow SemVer more strict than ever.

Most of the files in the repository is scaffolded using the generate tool with generate-charlike-templates generator. So please try to not edit anything.

Features

• options: add urlencodedLimit alias for formLimit (31ff6c1)
• parsing: split buffer parsing from text parsing (#52)(81f9a1f)
• extendTypes: implement extendTypes.custom and opts.handler, (#52)(be10d93)
• options: add opts.qs and opts.querystring - also possible with app.querystring (cc6ff4d)
• options: pass options to qs.parse or querystring.parse (e67f42c)
  • so you can now pass custom opts.delimiter (& to be $) for urlencoded bodies

Bug Fixes

• travis: fails because standard@8 release (6ae0c7f)
• qs-tests: fix for app.querystring and opts.querystring (c5df3a3)
• opts-tests: update tests for options (fe1696a)
• tests: fix possible build fails (522110c)

BREAKING CHANGES

• ctx.body: no more write to ctx.body (#50) (b927454)
• utils.handleMuliple: fix incorrect nesting (#55) (56726e9)

Couple of notes are needed here:

• this.request.files will always be array of files
• in this.request.fields there have field containing this.request.files array
• forms with type multipart/form-data now can accept nested fields see #61 if you pass qs module to opts.qs of course, otherwise they will work. In v2 they was just skipped I believe - in this.request i was recieving only the field for type="file"?