-
Notifications
You must be signed in to change notification settings - Fork 361
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
Remove unused code #4072
Remove unused code #4072
Conversation
3f4c23c
to
9e405ee
Compare
9e405ee
to
5f9b92c
Compare
@@ -17,7 +17,7 @@ | |||
|
|||
module VCAP::CloudController | |||
class Runner | |||
attr_reader :config, :config_file, :insert_seed_data, :secrets_file |
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.
Is it possible that this is used by a rake task or pipeline that wasn't loaded into the debride analysis context?
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.
There's no reference to it in cloud_controller_ng or capi-release. capi-release has references to CCNG's Drain code that debride didn't catch, but as far as I can tell that is the only place CCNG's code is referenced externally (and arguably should be replaced with a rake task)
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.
My favorite kind of code change, deletion
Changes in cloud_controller_ng: - Remove unused code PR: cloudfoundry/cloud_controller_ng#4072 Author: Seth Boyles <seth.boyles@broadcom.com> Dependency updates in cloud_controller_ng: - build(deps-dev): bump rubocop-rspec from 3.2.0 to 3.3.0 PR: cloudfoundry/cloud_controller_ng#4139 Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I was trying out this gem debride, which attempts to identify unused code in Ruby.
Due to the dynamic and meta-programmatic nature of Ruby/CCNG, there were a lot of false positives, and these were a few that I believe can safely be removed.
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
main
branchI have run all the unit tests using
bundle exec rake
I have run CF Acceptance Tests