-
Notifications
You must be signed in to change notification settings - Fork 359
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
test: additional examples for default responses #468
test: additional examples for default responses #468
Conversation
30c7739
to
0aaf369
Compare
4c58071
to
890dbfa
Compare
a33b95f
to
e97d23b
Compare
Comment on these failing tests: according to the code this is failing “on purpose”. The ability to look for the closest response is implemented only for successful responses; so you can do 2XX, and you’ll get the first one. Do you want to make the change and expand it to other responses as well, such as 4XX (which is the part of this test?) |
packages/http/package.json
Outdated
@@ -24,7 +24,7 @@ | |||
"caseless": "^0.12.0", | |||
"faker": "^4.1.0", | |||
"fp-ts": "^1.19.3", | |||
"json-schema-faker": "json-schema-faker/json-schema-faker", | |||
"json-schema-faker": "XVincentX/json-schema-faker", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, this is a leftover. Will fix.
@lag-of-death I had a go at fixing the conflicts but there is still a yarn.lock change floating around which I don't think should be there. These tests look great, if you can fix that I'll thumbs up and we're done here! 🎉 |
@phil, |
BLOCKED: #413 (comment) |
cf31d14
to
7b24d3c
Compare
36870ae
to
6c07710
Compare
This adds failing examples for #413. The passing ones are in #465.
Closes #413