chore(deps): update dependency hela to v3 #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0.9->^3.0.0Release Notes
tunnckoCore/hela
v3.2.2Compare Source
Note: Version bump only for package hela
v3.2.1Compare Source
Bug Fixes
v3.1.0Compare Source
3.1.0 (2020-02-29)
Features
v3.0.1Compare Source
v3.0.0Compare Source
For commiting please use
npm run commitscript.Starting from this release all the build/pull request/commit chain is changed to follow totally
semver,semantic-versionandstandard-version. Contributing guide is update too, please read it before do anything.The
README.mdandCHANGELOG.mdfiles are autogenerated files, so please DO NOT edit them manually - there are tools for that. Readme generation is handled byverbandverb-generate-readmegenerator, the change log and releasing is handled bystandard-versionand Git Hooks to follow SemVer more strictly.The commit message convention is based on Angular's using
conventional-changelogwhich works behind thestandard-version. Please follow them while sumbimtting Pull Requests and Bug Reports. If anything is not clear enough in theCONTRIBUTING.md, please open an issue to discuss it and propably change it.Advanced
npm scriptsis used to handled any linting and errors. So you won't be able to even push anything if simply runningnpm testfails. 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
generatetool withgenerate-charlike-templatesgenerator. So please try to not edit anything.Features
urlencodedLimitalias forformLimit(31ff6c1)opts.qsandopts.querystring- also possible withapp.querystring(cc6ff4d)qs.parseorquerystring.parse(e67f42c)opts.delimiter(&to be$) for urlencoded bodiesBug Fixes
standard@8release (6ae0c7f)app.querystringandopts.querystring(c5df3a3)BREAKING CHANGES
ctx.body(#50) (b927454)Couple of notes are needed here:
this.request.fileswill always be array of filesthis.request.fieldsthere have field containingthis.request.filesarraymultipart/form-datanow can accept nested fields see #61 if you passqsmodule toopts.qsof course, otherwise they will work. Inv2they was just skipped I believe - inthis.requesti was recieving only the field fortype="file"?Renovate configuration
📅 Schedule: "after 7pm,before 6am" (UTC).
🚦 Automerge: Disabled due to failing status checks.
♻️ Rebasing: Whenever PR is behind base branch, 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.