Ignore "Avoid having different types with same name" rule for extension classes
For static classes that only contain extension methods for a particular type, often the class name is in the format of "[Type]Extensions". These classes are most often transparent to the consuming code, and so the reasoning behind the critical rule "Avoid having different types with same name" need not apply, and certainly should not be critical.
"Such practice leads confusion and also naming collision in source files that use different types with same name."
1
vote
Travis Schettler
shared this idea
-
This has been fixed in version 2023.2.2 just released, thanks
