Skip to content
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

Add test to make sure the detekt default config is correct #348

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

mrmans0n
Copy link
Owner

@mrmans0n mrmans0n commented Oct 3, 2024

There have been some issues with either forgetting to add stuff to the detekt default config, or screwing up the active values (whether they are opt-in or not by default).

I've added a test to prevent this from happening again, which will parse the yaml file and assert that all rules are added to it, and that the active value is correct.

@mrmans0n mrmans0n merged commit e91ba45 into main Oct 3, 2024
2 checks passed
@mrmans0n mrmans0n deleted the nacho/test-detekt-config-is-correct branch October 3, 2024 16:28
@@ -11,7 +11,7 @@ Compose:
active: true
ContentEmitterReturningValues:
active: true
ContentSlotReusedCheck:
ContentSlotReused:
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woops, this rule wasn't properly configured -- which means it wasn't enabled by default, and it should have been. The test caught it, and now it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant