tag:rubydoc.tenderapp.com,2010-12-26:/discussions/problems/630-page-is-showing-old-docs-with-newish-versionRubydoc.info: Discussion 2019-01-19T06:03:19Ztag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T03:20:51Z2019-01-18T03:20:51Zpage is showing old docs with new(ish) version #<div><p>It seems to be showing 5.5.1 in the breadcrumb now. Can you confirm that it's displaying the right docs?</p></div>lsegaltag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:03:22Z2019-01-18T19:03:23Zpage is showing old docs with new(ish) version #<div><p>Yes and no. The right-hand frame, which shows the breadcrumb and the Readme<br>
file, is now up to date. Unfortunately, the left-hand frame with the list<br>
of modules and classes is still showing what appears to be the 5.4.3<br>
documentation: for instance, the SSE module and all of its classes were<br>
completely removed in v5.5.0, but they're still showing in that list.</p>
<p>It does seem to have processed the new content when it comes to displaying<br>
individual pages. For instance, if I click on "SSE" in the list, I get a<br>
"not found" page, suggesting that it really has been removed— just not from the list. And if I click on other classes that haven't been removed, I do<br>
see up-to-date docs for them in the right-hand frame.</p></div>Eli Bishoptag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:08:53Z2019-01-18T19:08:53Zpage is showing old docs with new(ish) version #<div><p>I just dumped some cache and it seems to be cleared up now. Let us know if you have any other issues!</p></div>lsegaltag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:13:16Z2019-01-18T19:13:17Zpage is showing old docs with new(ish) version #<div><p>That's a lot better, thanks. I'm no longer seeing any old content.</p>
<p>However— and this is probably not related at all, but since I've already<br>
got you— what I'm seeing is not exactly what I would expect from YARD.<br>
There are a lot of classes that are implementation details and we'd rather<br>
not have them cluttering up the docs, so, starting with 5.5.0, we tagged<br>
them as @private. I proofed all this stuff by running YARD locally prior to<br>
release, and those things were correctly omitted. But they're all still<br>
showing up on your site. I presume this means you're running YARD with<br>
different parameters than I was, but is there any way we can get the<br>
desired result?</p></div>Eli Bishoptag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:19:38Z2019-01-18T19:19:38Zpage is showing old docs with new(ish) version #<div><p>You'll want to use a <code>.yardopts</code> file in your repository, and for RubyGems in particular, you will want to make sure the file is packaged with the .gem (included as part of <code>spec.files</code>): <a href="https://rubydoc.tenderapp.com/kb/getting-started-with-rubydocinfo/setting-up-a-yardopts-file">https://rubydoc.tenderapp.com/kb/getting-started-with-rubydocinfo/s...</a></p>
<p>If you were testing this on the command line you probably were using <code>--no-private</code>, which is one of the options you would want in the .yardopts file. You can take a look at YARD's for an example: <a href="https://github.com/lsegal/yard/blob/master/.yardopts">https://github.com/lsegal/yard/blob/master/.yardopts</a></p></div>lsegaltag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:27:37Z2019-01-18T19:27:37Zpage is showing old docs with new(ish) version #<div><p>Great, thanks.</p></div>Eli Bishoptag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T19:45:26Z2019-01-18T19:45:26Zpage is showing old docs with new(ish) version #<div><p>Sorry, one more question. When I run YARD locally, in order for Markdown<br>
formatting to work I have to specify "--markup markdown" and<br>
"--markup-provider redcarpet". But since things did show up correctly on your site even without having a .yardopts file, it seems like maybe it<br>
works anyway in the default configuration. Should I omit those parameters?</p></div>Eli Bishoptag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T21:12:40Z2019-01-18T21:12:42Zpage is showing old docs with new(ish) version #<div><p>I'm pretty sure the answer to my last question is yes, so I added the .yardopts file and released version 5.5.2.</p>
<p>However, I think there may still be some kind of caching problem happening, the same as before. That is, when I view [<a href="https://www.rubydoc.info/gems/ldclient-rb">https://www.rubydoc.info/gems/ldclient-rb</a>] I see the correct 5.5.2 content in the right-hand frame; and if I view a page like [<a href="https://www.rubydoc.info/gems/ldclient-rb/LaunchDarkly">https://www.rubydoc.info/gems/ldclient-rb/LaunchDarkly</a>] it is correctly omitting stuff that was marked @private (for instance, the Impl module); but the list in the left-hand frame seems to be showing content for 5.5.1 or 5.5.0.</p></div>Eli Bishoptag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T21:17:26Z2019-01-18T21:17:26Zpage is showing old docs with new(ish) version #<div><p>We've been having some update issues with gems recently-- I've force a refresh on this one and it should be updated to 5.5.2 everywhere now. I'll take a look at some of this refresh logic to see what's going on-- thanks for calling this out!</p></div>lsegaltag:rubydoc.tenderapp.com,2010-12-26:Comment/468204632019-01-18T21:27:57Z2019-01-18T21:27:58Zpage is showing old docs with new(ish) version #<div><p>Looks perfect now, thanks!</p></div>Eli Bishop