-
-
Notifications
You must be signed in to change notification settings - Fork 844
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
Rake Task: avoid calling super with arguments to avoid an ArgumentError #943
Conversation
The RakeLib base class does not define a specific initializer.
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.
👍
This allows us to keep the RuboCop rule.
Tested this (with |
Thanks! Should I expect a new release soon ? |
Everything depends on things not going bad when releasing. If they do, I lose hope and then things take more time. Now, I had to:
So, this is a hassle. And I've already quit this maintainership. |
@mfortin PS: the 1.16.1 is out. Try it! |
all good, thanks for your prompt response @olleolleolle |
Thank you @olleolleolle |
Thank you very much @olleolleolle 🙌 I see your pain with this. lmk, how we can we improve this. Btw, @mfortin @kennyadsl wants to point out that this repo needs collaborators. so if some want to participate - you are very welcome! #727 If you are using this repo, it would be great if someone can help to help to maintain and release new things for this repo. |
Updated the Settings to remove the "requires a review to be merged". All other protections remain. |
Rake's RakeLib base class does not define a specific initializer.
In the initializer for our RakeTask creation class, we call super sans args.
When we do call it with a specific name,
super
fails like:Fixes #942