tag:rubydoc.tenderapp.com,2010-12-26:/discussions/problems/697-documentation-is-not-generated-for-a-libraryRubydoc.info: Discussion 2019-09-26T20:48:15Ztag:rubydoc.tenderapp.com,2010-12-26:Comment/476588792019-09-26T20:48:14Z2019-09-26T20:48:14ZDocumentation is not generated for a library<div><p>Rubydoc has enabled sandboxed execution of YARD extensions, which it looks like Capybara is using, but we currently only support that execution during parsing and not generation. It looks like Capybara's extension is generating custom objects into the .yardoc database that cannot be deserialized by the generation layer, in other words, the extension expects the generation layer to use the same execution context as the parser. This works well for local execution but is problematic for our shared environment-- the right way to do this would be to not create custom objects but to rely on YARD's existing tag system to apply properties.</p>
<p>The TLDR here is that it doesn't seem like the 2.x gems are compatible for the time being. The good news is that the latest 3.x gem seems to work, but that may or may not help you if you're relying on older APIs that are no longer in 3.x.</p>
<p>If this is really a problem we can try to provide a one-off workaround here until we have a more long-term fix.</p></div>lsegal