-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Unexpected missing top-level module documentation comment #947
Comments
It's not intended but currently RuboCop cannot handle state between multiple files. See: #323 |
Thanks for the reply. In my usage case this is unfortunate because RuboCop is used to fail the CI build with any violation so this means that this module cannot be enabled. Although state between files is a very desirable feature, there would be another alternative to fix the |
Maybe such an option would make sense. Alternatively we can add constants to our namespace module check. Modules that are considered namespaces by RuboCop are not required to have documentation. |
Any update on this @bbatsov ? |
I've been quite busy lately and I haven't tackled this yet. |
It would be nice to separate the class and module documentation checks, at least. |
Might it make sense to allow namespaces that have only constant children of any kind (Class, Module, Constant) to be undocumented? |
Slightly expanding what we mean by namespace module. I'd be ok with that. |
OK, sounds like @jonas054 likes the idea, at least a little bit. Almost all the specs for this cop will have to be adjusted. But that's OK. |
Pushed a fix to my open PR. @bbatsov, if you decide that classes/modules with only constants are not "namespaces", I will delete that commit from the PR. |
This report is relative to the
Documentation
cop. The output of Rubocop is the following:The module Pod is commented here and the file which lead to the warning is this one.
Is this the intended behaviour?
The text was updated successfully, but these errors were encountered: