-
Notifications
You must be signed in to change notification settings - Fork 4
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
Suppress YARD warning logs #26
Conversation
Sorry, I didn't know how to guarantee the behavior in this repository since there was no test. |
You can try |
Fixed ksss#25 When rubocop is executed, the warning of YARD itself should not be output, but should be reported as an offenct of rubocop.
6430865
to
9d32ae5
Compare
@ksss |
To reproduce the problem, could you add a test case that does not produce warnings, or provide a sample YARD case that does produce warnings? |
Oh, sorry. I forgot to share how to reproduce. diff --git a/smoke/mismatch_name.rb b/smoke/mismatch_name.rb
index debfa1b..0191f5e 100644
--- a/smoke/mismatch_name.rb
+++ b/smoke/mismatch_name.rb
@@ -45,6 +45,10 @@ class Foo
# arg doc
def returned(arg)
end
+
+ # @return Hash{Symbol => String}
+ def invalid_format(arg)
+ end
end
# https://github.com/ksss/rubocop-yard/issues/18 After applying the above changes in the main branch, the following command will output a warn log.
The warn log is not included in the rubocop results. Should I set up a minitest or rspec and write a unit test? |
Thank you for sharing repro. |
v0.9.3 has been shipped |
Fixed #25
When rubocop is executed, the warning of YARD itself should not be output,
but should be reported as an offenct of rubocop.