You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that false positive in ScalaDocChecker is solved #123 (at least, merged).
So, what about introduce ScalaDocChecker level?
Now developer have to comment almost everything. Classes, traits, methods, types, properties (val's inside classes). It's overwhelming (from my point of view - mostly useless).
For instance, I'd like to configure entities that I want to check by ScalaDoc. Like, only classes, case classes, objects, traits. Nothing else. Someone else wants check also methods and properties. Just configure it.
The text was updated successfully, but these errors were encountered:
You can to a certain extent, by ignoring certain classes according to a regular expression - see the ignoreRegex parameter. However, I agree that we shouldn't have to do everything.
It seems that false positive in ScalaDocChecker is solved #123 (at least, merged).
So, what about introduce ScalaDocChecker level?
Now developer have to comment almost everything. Classes, traits, methods, types, properties (val's inside classes). It's overwhelming (from my point of view - mostly useless).
For instance, I'd like to configure entities that I want to check by ScalaDoc. Like, only classes, case classes, objects, traits. Nothing else. Someone else wants check also methods and properties. Just configure it.
The text was updated successfully, but these errors were encountered: