Closed mattwynne closed 10 years ago
We have to ask ourselves - how valuable are these warnings? Since ruby isn't able to only warn about certain files, there is bound to be noise from dependent libs. Maybe the output could be passed through grep
to filter out the lines that are not from the code in the git repo? And then fail the build if there are any warnings in our code.
That's all this ticket is for - to fix the warnings coming out of the code in this project.
I've fixed two warnings, only the first one isn't fixed now, but it looks like this is the case where ruby is unable to work with its meta magic ;)
We're using warnings in the build for cucumber/cucumber-ruby-core and there's a lot of noise coming from Gherkin.
Examples:
See also cucumber/cucumber-ruby-core/issues/6