Loren Segal
Loren Segal
I can't seem to reproduce the issue in ruby 3.3.0 on my machine. Given that rubydoc.info also does not have the issue you're reporting, could there be something in your...
Thanks for the repro. This is now fixed and will be in the next release.
> We are investigating whether it's possible to have each method on a single page, and have it breadcrumbed under the Client's CodeObject. If this is possible, what is the...
> I am also wondering if any of these changes can be merged upstream or if any of them are considered breaking? As far as language settings go, this might...
First a technical note here: if you are using the `@!parse` directive, you must provide valid Ruby code-- in this case, you are missing an `end` token in your class...
Thanks for the work on this, sorry it took so long to get in!
Based on my _best_ recollection, the C parser doesn't parse loose comments because we don't have context on what those comments are "attached" to-- in other words, we can't really...
Adding a timezone to the timestamp seems reasonable. Would accept a PR to fix this. As far as git commit hash and library version, these aren't something that YARD necessarily...
Rubydoc intentionally pulls information that yard alone does not have-- specifically the rubygems package release list or git repos. That's because rubydoc explicitly pulls from these sources. YARD only uses...
@bladeacer sorry for the delayed response here. If you're still running into this issue, can you provide a bit more info? I'd like to understand what you mean by "system...