-
Notifications
You must be signed in to change notification settings - Fork 44
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
Update for staticcheck compliance #119
Conversation
Hi, thank you! We'll take a look! But meanwhile, there are 2 test failures from running
|
Hi @geofffranks Any update on these failures? |
oh, thanks! i missed this comment. Will take a look today. |
…use it for things not in systemcertpool
c.Value's type is already `interface{}`, so explicitly checking to see if it can be type-asserted to the type it has is redundant. Additionally,this results in c.Value being stored to result.Value both when it is really a string, or otherwise, so just set it and move on.
056b039
to
51615e3
Compare
Ok, should pass tests now @Tallicia @peterhaochen47 - thanks! |
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.
Updates for staticCheck look ok
👋Howdy!
We (the App Platform Runtime WG) pull credhub-cli into the diego-release codebase, and are trying to run staticcheck on all of its codebases. We found a few things flagged on credhub-cli, and would love it if y'all could incorporate these changes so we don't have to jump through hoops to whitelist certain codebases from our staticcheck automation.