-
-
Notifications
You must be signed in to change notification settings - Fork 783
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
Empty custom config enables rules disabled by default #3379
Comments
Thank you for the express fix! |
This was referenced Mar 11, 2021
Closed
Closed
This was referenced Mar 11, 2021
This was referenced Mar 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
When I create an empty custom config file and enable it though
detekt { config ... }
, it should work as if the custom config wasn't enabled.Observed Behavior
My Gradle config is as follows:
and the config file is empty. When I run Detekt, I'm getting
I customized one rule that I needed and it now seems to work correctly.
Steps to Reproduce
See above.
Context
This issue caused confusion as the behavior is counter-intuitive, or if it's somehow by design, it's not documented well enough.
Your Environment
The text was updated successfully, but these errors were encountered: