-
Notifications
You must be signed in to change notification settings - Fork 96
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
Undefined method 'metrics=' for MetricFu::Configuration #186
Comments
Seems to have been fixed by changing the .metrics file to:
It seems very strange that the default file would be broken. Not sure if this is the right fix. |
You shouldn't need that in your .metrics file at all. Nonetheless, yes, it is my fault for breaking that outside of a major release. I'll leave this open to remind me to add deprecations. |
Cool. Happy to submit a PR if you have any guidance for what the .metrics file should look like by default. |
I actually just realized that this was because the project I'm working on had a .metrics file previously. I simply hadn't noticed. Sorry! |
Anything else in your .metrics I should deprecate? |
metrics, graphs, flay, flog, reek, roodi, saikuro, churn, and rcov all appear to have (at some point) been accessible on MetricFu::Configuration. I'm getting the same error for all of them. |
Yes, see 'breaking changes' under These breaking changes should have been in a major release, and only |
Ah, that makes sense - thanks! I'm not sure what the intention was of the various config options before, so I just turned everything to the defaults now (but skipping Flay because it doesn't seem to finish). |
If Flay doesn't finish, please report a bug! If you could run with |
Can do. I wasn't sure if it was my settings or it. Installed via gem install, run via command line I'll run that and let you know what I get. |
|
Hi, sorry this issue has gotten stale. Would you still be interested in helping add a deprecation mechanism and the deprecated methods? |
Hey sorry for the delayed response - been crazy busy lately. I'm definitely interested in helping, but not sure I'll be able to make time for it soon. However, if you don't mind leaving this open, I will certainly look to come back to it in a few weeks. In the mean time, did you have anything in particular in mind for how to handle deprecation? |
My first though is to wrap the method like rubygems does. My second is to |
I ran
gem install metric_fu
And then ran
metric_fu
in my project directory, and got the following error. I'm sure there's something I'm doing wrong, but not sure what the right steps are:The text was updated successfully, but these errors were encountered: