Skip to content
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

stack level too deep when generating documentation for modules with same names but different namespaces #216

Closed
paneq opened this issue Dec 14, 2010 · 6 comments

Comments

@paneq
Copy link

@paneq paneq commented Dec 14, 2010

File lib/translatable.rb:

module Translatable
end

File lib/active_record/extensions/translatable.rb :

require 'translatable'
module ActiveRecord
  module Extensions
    module Translatable
      include ::Translatable
    end
  end
end
::ActiveRecord::Base.send(:include, ::ActiveRecord::Extensions::Translatable)

Calling:

.rvm/gems/ruby-1.9.2-head/gems/yard-0.6.3/bin/yard doc lib/translatable.rb lib/active_record/extensions/translatable.rb

leads to an exception

.rvm/gems/ruby-1.9.2-head/gems/yard-0.6.3/lib/yard/code_objects/proxy.rb:231: stack level too deep (SystemStackError)
@lsegal
Copy link
Owner

@lsegal lsegal commented Dec 20, 2010

Fix Derived < ::Base inheriting wrong Base (not top level)

Closed by 57a7a56

@lsegal
Copy link
Owner

@lsegal lsegal commented Dec 20, 2010

This issue was a side effect of ::TopLevelConstants not being properly recognized. It should work now.

@paneq
Copy link
Author

@paneq paneq commented Dec 20, 2010

Thank you! I will check it out soon

@paneq
Copy link
Author

@paneq paneq commented Dec 20, 2010

When can we expect 0.6.4 released ?

@lsegal
Copy link
Owner

@lsegal lsegal commented Dec 22, 2010

Right now :)

@paneq
Copy link
Author

@paneq paneq commented Dec 22, 2010

0.6.4 works for me. The bug is fixed indeed.
Thank you very much.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.