We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CI on ruby-head fails with the following output.
This happened at least since this build on 2021-06-30: https://github.com/ruby/did_you_mean/runs/2948189838?check_suite_focus=true
This is the test output:
Failure: test_message(VerboseFormatterTest): </undefined\ method\ `zeor\?'\ for\ 1:Integer\n\n\ \ \ \ Did\ you\ mean\?\ zero\?/> was expected to be =~ <"undefined method `zeor?' for 1:Integer\n" + "\n" + " @error = assert_raise(NoMethodError){ 1.zeor? }\n" + " ^^^^^^\n" + "\n" + " Did you mean? zero?\n" + " ">. /home/runner/work/did_you_mean/did_you_mean/test/test_verbose_formatter.rb:17:in `test_message' 14: def test_message 15: @error = assert_raise(NoMethodError){ 1.zeor? } 16: => 17: assert_match <<~MESSAGE.strip, @error.message 18: undefined method `zeor?' for 1:Integer 19: 20: Did you mean? zero? ===============================================================================
The text was updated successfully, but these errors were encountered:
It's probably due to the newly added https://github.com/ruby/error_highlight. Shouldn't be too difficult to fix by just disabling it.
cc @mame
Sorry, something went wrong.
Disable error_highlight when testing did_you_mean
93df310
Fixes ruby#160
Thanks, @mame , for finding & repairing this!
🚀
Successfully merging a pull request may close this issue.
CI on ruby-head fails with the following output.
This happened at least since this build on 2021-06-30: https://github.com/ruby/did_you_mean/runs/2948189838?check_suite_focus=true
Details
This is the test output:
The text was updated successfully, but these errors were encountered: