-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
"too many arguments for format string" warning #12910
Comments
There are quite a few of these. Some cops define multiple offense format strings with different "arity" and they just all get the same amount of arguments passed. I looked at this in the past and some are trivial to fix, some require a bit more finesse. |
Ah, I see, thanks. Feel free to close if it's already been discussed previously. |
I haven't talked about this with anyone. It's not a very common usecase since it's mostly a cli tool but I think it would be nice to have RuboCop warning-free anyways for those that use it in other ways. You probably won't be able to raise on warnings since RuboCop inspects some rather strange-looking code (mostly regex stuff) but most looked fixable from what I remember. |
See rubocop#12910 This aren't all cops where this happens, just the ones with trivial solutions
I'm trying to some of these off:
Remaining:
Wasn't quite as much as I thought it would be. The regex warnings made up the bulk of all the warnings in the test suite |
See #12910 This aren't all cops where this happens, just the ones with trivial solutions
Closes rubocop#12910 This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
This is inspired by how Rails approaches this
It doesn't cause a problem, but when running with warnings enabled, the following is emitted:
(I think it may be a clash between the
format
defined by RuboCop andformat
defined inKernel
?)The same can be seen when running RuboCop's own tests with
config.warnings = true
.The text was updated successfully, but these errors were encountered: