-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update chai-http to the latest version 🚀 #24
base: master
Are you sure you want to change the base?
Conversation
Version 4.1.0 just got published.Update to this version instead 🚀 Release Notes4.1.0 / 2018-08-03This is a minor update to fix a bug with Community ContributionsCode Features & FixesCommitsThe new version differs by 6 commits.
See the full diff |
Version 4.2.0 just got published.Update to this version instead 🚀 Release Notes4.2.0 / 2018-08-29This is a minor update that adds TypeScript definitions. Community ContributionsCode Features & Fixes |
Update to this version instead 🚀 Release Notes for 4.2.1 / 2019-01-02This patch fixes usability issues for TypeScript definitions. Community ContributionsCode Features & FixesCommitsThe new version differs by 5 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for 4.3.0 / 2019-04-26This feature release allows you to pass a Regular Expression to the expect(res).to.redirectTo(/^\/search\/results\?orderBy=desc$/); Community ContributionsCode Features & Fixes
|
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 4.0.0 of chai-http was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of chai-http.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
4.0.0 / 2018-03-22This is a major update to the underlying dependencies and also introduces some breaking changes.
404
, or500
or any other status code cannot be asserted on in thecatch
block, instead must be asserted on in thethen
block. In other words this behaves more akin tofetch
.chai.request(server)
object will automatically close the server connection after the first request. This means if you have code like this:you'll need to change it to:
This is described further in the README
Community Contributions
Code Features & Fixes
statusCode
when asserting .status (by @atom-morgan)agent
(by @yashsriv).redirect()
assertion (by @tonymet)Documentation fixes
.not.redirect
in readme (by @mcky)Commits
The new version differs by 54 commits.
d9a8d1f
4.0.0 (#202)
a315dd0
chore(package): fixed license typo (#199)
832f6c2
docs: add note about agent server not closing (close #188) (#190)
cee5dbd
Merge pull request #184 from chaijs/fix-178
3d7ab70
feat(node-request): close connections after request
d3d9ec6
chore(package): update devdependencies
e2e80ce
chore(package): update all package versions
80c880c
chore(package): update superagent to 3.7 (#183)
80b4efb
docs: add chai.expect usage to readme (#173)
2604c3b
mention login in the persistent session guide (#167)
77a7a93
docs: fix form test example in README (#166)
6e88c38
Merge pull request #131 from meeber/chai-v4
7426715
Update for Chai v4.0
cf52191
Merge pull request #160 from mcky/patch-1
dfffa63
Add to.not.redirect example to README
There are 54 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴