-
Notifications
You must be signed in to change notification settings - Fork 7
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
New rubocop #112
New rubocop #112
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.
How many changes! LGTM 👍
@@ -43,6 +43,8 @@ class FormatDialog < ::UI::Dialog | |||
# | |||
# @param dasds [Array<Y2S390::Dasd>] list of DASDs to be formatted | |||
def initialize(dasds) | |||
super() |
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.
Are we sure this change is safe? It's actually the first real change I have seen (with implications that may go beyond style and readability).
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.
yes, change is safe and I do not many times for newer rubocop. Basically when you have class that is child of another, rubocop wants you to call its initialize to ensure that it is properly initialized. And I need to use super()
as super
will pass its arguments and UI::Dialog constructor is without params.
For more such changes see e.g. yast/yast-storage-ng@e76cfb2
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.
LGTM with one comment
✔️ Internal Jenkins job #32 successfully finished |
Problem
CI for master failing due to old rubocop not working with the ruby on TW.
Solution
update rubocop.