Yes - meant plugins registry. right now the plugin links point to github, so you always see master
I don't think we should concern ourselves with correcting docs for old versions of plugins. It's a similar argument to fix bugs in old versions of plugins (any changes create a new version). On Mon, Jun 23, 2014 at 11:37 AM, Ray Camden <[email protected]> wrote: > So I just want to double check to make sure I'm groking it right myself - > this was simply a mistake in terms of the doc for version X+1 going live > before plugin version X+1 was ready, right? When/how will it be corrected? > (Not trying to be pushy, just want to make sure I explain it well to others > if asked. :) > > > ________________________________________ > From: Carlos Santana <[email protected]> > Sent: Saturday, June 21, 2014 12:09 PM > To: [email protected] > Subject: Re: Contacts API, iOS > > Andrew plugins are not in npm, did you meant the plugin registry. > > Then yes I agree that way user can read the docs that go along with the > version of the plugin. If they have an older version of the plugin the can > use the drop down to switch the version to an older version and read the > corresponding docs for that version. >
