-
Notifications
You must be signed in to change notification settings - Fork 33
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
[BUG]: StringEnum parsing is inconsistent #543
Comments
👋 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 |
Thanks for opening this. We added I can't get your reproduction to work, but I do get a warning in my IDE of
Which makes sense if you're hitting this line
I can't quite figure out why you're getting different results though, as
Could you maybe try |
Okay, we can probably just use |
You're welcome. I'll keep this open for now to see if I can repro your original issue. |
What happened?
After upgrading
Octokit.Webhooks
from1.5.1
to2.2.3
we noticed a test start failing. However it wouldn't fail when debugging. We narrowed it down to something about the way StringEnum is working.Checking a
PullRequestEvent
->Sender
->Type
againstOctokit.Webhooks.Models.UserType.Bot
was previously correctly returningtrue
, but now returnsfalse
. But if debugging, or if using the sender type before the check, the check returns true again. (Such as printing the value to console)Reproduction
test data:
Versions
upgrading
Octokit.Webhooks
from1.5.1
to2.2.3
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: