-
Notifications
You must be signed in to change notification settings - Fork 341
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
Runners not unregistering due to camelCase #585
Conversation
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.
What if we delay the conversion to snake_case until the invocation of the GitHub API? Anyhow, it might be a bit more verbose, so I don't have a strong preference over any of the methods.
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.
Looks good to me!
Its ugly, normally in modern js you destructure looking to match the needed member later on. In this case Im going to reuse id straight to avoid lint but in the future we should destructure snake_case and add a lint ignore rule |
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 also prefer the "ugly but correct/consistent" way suggested by @0x2b3bfa0 and used in the rest of the codebase (and my Python bias avoids variables called id
) but whatever
In this case was done just because is easy to read. If it were 20 lines I would not have done it either. But here is totally fine because you use it afterwards assignment Indeed just after
So you understand that the id is the runner's id |
unless your memory is worse than mine 👴 |
GH api uses snake_case 🐍 due to this GH are not unregistering successfully anymore
Fixed in #583 however it might take longer and this is important.