Loren Segal

> Classes marked with @api public should show in the class list regardless of whether the containing module is marked as such. Unfortunately that's not the expectation YARD provides, though...

> The reasoning that the container must be public for the child to be public does make sense. I would have inferred that but for the fact that all of...

Also just adding a bit extra to one part of your initial response which I think is relevant: > Call this the "ancestor-match rule". IMO this rule is counterintuitive, as...

Patches would be accepted to support this.

There are definitely concerns about breaking changes here. I realize that you show a non-breaking option, but I'm not 100% sure that dc5788a5c386997d72625c0579f4df2b17adc8ed is really the only breaking change. It...

The default `@!method` scope is instance, since YARD isn't able to know if the dynamic method will be instance or class level. You can change this by embedding the `@!scope`...

@olivierlacan can you show a reproducible example? The above snippet correctly generates a class method `Potato.fry` for me.

YARD typically doesn't have porcelain style output because if you need specific structure to be parsed by "machine", it's easy enough to use its programmatic API to access via standard...

It doesn't seem like your methods are correctly being detected as private/protected, YARD should already be showing these tags. This is the output for the following minimal repro: ```ruby class...

YARD has guides on the website that walk through the process, both for building parsers and for custom templates (your plugin can do one or ther other, or even both):...