Re-opened Classes Trigger Doc Violation about cane HOT 4 CLOSED

Failing spec:

diff --git a/spec/doc_check_spec.rb b/spec/doc_check_spec.rb
index 5af9803..556709b 100644
--- a/spec/doc_check_spec.rb
+++ b/spec/doc_check_spec.rb
@@ -53,4 +53,15 @@ class Doc; end
       file_name, 4, "AlsoNoDoc"
     ]
   end
+
+  it 'ignores classes documented elsewhere' do
+    file_name = make_file <<-RUBY
+class Doc; end
+# Documented later.
+class Doc; end
+    RUBY
+
+    violations = check(file_name).violations
+    violations.length.should be_zero
+  end
 end

from cane.

Hmmm, I'm not sure about this one. In all cases I do this I consider a comment even more important than normal, documenting things such as why the monkey-patch is valid, which github issue it links to, and when I should consider removing it.

from cane.

In an example project I'm working on, a class is used as a namespace for other classes and these other classes are defined in separate files. The class itself is not getting reopened for any other purpose. We could reconsider the overall project structure, but this is definitely making Cane more difficult to work with out of the box.

from cane.

Heh, that is the reason cane doesn't enforce documentation on modules. See #10 for discussion of that. I'll sleep on it.

from cane.