Skip to content

Conversation

oowekyala
Copy link
Member

This check caused a checkstyle failure on pmd/pmd#6037 even though the switch is exhaustive

@jsotuyod
Copy link
Member

jsotuyod commented Sep 6, 2025

Rather than a warning, shouldn't we completely remove the <module>? I'm 100% in favor of removing checkstyle rules when our own are equivalent (if not better, as is this case).

We may also want to consider adding ExhaustiveSwitchHasDefault to our dogfood PMD config.

adangel added a commit to adangel/build-tools that referenced this pull request Sep 12, 2025
- ExhaustiveSwitchHasDefault (refs pmd#98)
- RelianceOnDefaultCharset
- ModifierOrder
- DanglingJavadoc
- CollectionTypeMismatch
- OverrideBothEqualsAndHashCodeOnComparable
@adangel
Copy link
Member

adangel commented Sep 12, 2025

I think, we should remove this checkstyle rule completely and not even create a warning (who looks at warnings if they don't fail the build?)

We have already our PMD rule NonExhaustiveSwitch enabled and #99 adds ExhaustiveSwitchHasDefault.

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.

3 participants