-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: ensure statusCode is always an integer #439
Conversation
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
could you consider reviewing this please? |
This only changes it on the error. Should there not be a middleware in |
I am still investigating on the original issue. But this can be make it more resilient anyway. So I would still recommend the PR. |
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.
I'm okay with it, just would use isNan
Can we please merge it? THen I could check if this workaround works on gcf. :) |
🎉 This issue has been resolved in version 6.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I have some bug, where the status code is set to a string value. One way to fix it, is by enforcing status to be always an integer.