-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
make status codes numeric #381
Conversation
Codecov Report
@@ Coverage Diff @@
## main #381 +/- ##
==========================================
+ Coverage 92.91% 93.43% +0.52%
==========================================
Files 5 5
Lines 268 259 -9
Branches 90 84 -6
==========================================
- Hits 249 242 -7
Misses 13 13
+ Partials 6 4 -2
Continue to review full report at Codecov.
|
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.
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.
This changes works well for my usage in @octokit. Accessing the responses works the same using ...["responses"]["200"]
. The only difference is that keyof paths["..."]["get"]["responses"]
returns 200 | 404
instead of "200" | "404"
I say let's go ahead with it. I'm not even sure if I would consider the change a breaking change, but when in doubt I'd always rather go with a breaking change.
Yeah I could go either way here. I think it technically is a breaking change, but it’s a breaking change on a newly-released feature. I agree with erring on the side of breaking change, and cutting |
@all-contributors please add @jankuca for code, test |
I've put up a pull request to add @jankuca! 🎉 |
OK I tagged & released |
Closes #380