-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
RSpec/EmptyExampleGroup warning when using rswag's run_test! #1177
Comments
We've discussed pretty extensively how it would be possible to smoothen the rough edges between Rswag and Thanks for reporting. Please don't hesitate to ask further questions. This area is interesting and important to make If you want to kick-off |
Hey @pirj, thanks for the reply. Could you expand a bit more about this?
|
https://github.com/rubocop/rubocop/releases/tag/v1.19.0 released with the fix to DSL configuration loading. |
@pirj Thanks for the news! does that fix the RSpec/EmptyExampleGroup when only |
Provided you configure its DSL properly #1165, supposedly yes. |
this is fixed in newer rubocop-rspec versions. see: rubocop/rubocop-rspec#1177
this is fixed in newer rubocop-rspec versions. see: rubocop/rubocop-rspec#1177
rubocop does not recognize rswag's
run_test!
as a test block and results in an unexpected behavior. If this really is a bug, I would love to explore it and try to fix it.Expected behavior
I expect this to give no offenses
Actual behavior
Steps to reproduce the problem
A simple spec like this should suffice.
RuboCop version
The text was updated successfully, but these errors were encountered: