Ray, Yeah seems file plugin @c1a1052 was tagged for 1.1.0 release 13 days ago, you patched docs after that tag @abcaf70 12 days ago, and plugin was actually released with @e9efe65 7 days ago. You just missed the window narrowly!
-Michal On Wed, Apr 30, 2014 at 9:45 AM, Michal Mocny <mmo...@chromium.org> wrote: > I believe the plugin docs reflect what was bundled with the latest plugin > release -- perhaps your recent changes were not released yet? Or has > something gotten lost in the recent shuffle with dev/master branches? > > Its true, though, that for core plugins our registry links to the official > apache repos and not the github mirrors, and the official repo links do not > have a pretty renderers for markdown docs. Not sure what we want to do > here. > > > On Wed, Apr 30, 2014 at 9:14 AM, Ray Camden <rayca...@adobe.com> wrote: > >> I just noticed that the links for plugins from docs.cordova.io go to a >> new page (http://plugins.cordova.io/#/package/org.apache.cordova.file as >> an example). The docs for this one in particular seem wrong. I recently did >> a small mod to add the error codes to the docs, and I'm not seeing it here. >> Mistake? Do I need to make a new PR on the repo? >> >> Related - why is the link to the github version gone? > > >
