-
Notifications
You must be signed in to change notification settings - Fork 4
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
For loops that never loop - confusing code #18
Comments
Thanks.
Line 166 in e94589a
Line 168 in e94589a
The response from AWS should also contain 1 element. This can be more explicit. I've added #19 too. |
I got muse.dev installed by the org admin and run against a new branch I created: https://console.muse.dev/result/Autodesk/go-awsecs/01EN1N912T0JXKZMXN0M1D3VG5?tab=results The reported issues are now cleared. I'm adding |
Yes, Muse.dev will run on the checks all the time (on PRs) for every repo on which it's installed. The status bar links to the console which has all the historic bugs, but the main interface is the PR. In the PR you are getting comments on new bugs thought to be introduced (or at least exposed) by the current PR.
Thank you for asking. We don't have a badge at this time but have recorded the feature request. Reach out any time if you have thoughts on analyzers, interface, or anything doesn't seem right. |
I'm looking here:
go-awsecs/asg.go
Line 180 in e94589a
And while playing with staticcheck (a go Analyzer) I see this and another loop are ... non loops. Is there an idiom here I'm missing that makes this style sensible?
The text was updated successfully, but these errors were encountered: