for a set of classes
app/base.rb:
  class Base
  end
app/sub/base.rb:
  module Sub
    class Base
    end
  end
and
app/sub/foo.rb:
  module Sub
    class Foo < Base
    end
  end

yardoc creates documentation where Foo inherits from ::Base not
Sub::Base.
It's easy to work around using class Base < Sub::Base but it would be
nicer if yardoc picked the right base class.

Processing order seems to be relevant as well. In my large real world
use case, I had a case where one Foo-like class went ok while another
failed. I was not able to reproduce that in a short sample though.

best
  Morus

On 6/18/2012 5:58 AM, Morus Walter wrote:

Loren