cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Grebnov (Akvelon)" <>
Subject RE: Contacts API, iOS
Date Tue, 24 Jun 2014 20:15:48 GMT
The signature change was made by me to be compliant with the rest of cordova core plugins where
we always have callbacks first and then call parameters.

The important note is that I used special check for the args type to work correctly in case
old method signature is used. I will see when it was missed.

Do you like the idea of changing method signature and making it work for old version or it
is better just to revert it back? - Thoughts?

-----Original Message-----
From: Carlos Santana [] 
Sent: Tuesday, June 24, 2014 11:55 PM
Subject: Re: Contacts API, iOS

I took a few minutes to look deeper on what's going on with Contacts Plugin.
Here are my findings:

Back in April [1] when navigator.contacts.pickContact() was added the signature for navigator.contacts.find()
was changed
navigator.contacts.find:function(fields, successCB, errorCB, options) {
navigator.contacts.find:function(successCB, errorCB, fields, options) {

I think this is a braking change and the reason why mobilespec is failing.

If there are no objections I think the find method should be put back as it was before publishing
a new version with a different api signature. I created an issue [2] to track

Or if the consensus is for find function to have a new signature, then the version of the
plugin needs to be increase to reflect the api break, and maybe a note in the doc.

I also created another issue [3] to create tests for pickContact in mobilespec





On Mon, Jun 23, 2014 at 4:21 PM, Sergey Grebnov (Akvelon) <>

> As a note - pickContact functionality exists in repo/master only and 
> has not been released to plugins registry yet.
> Thx!
> Sergey
> -----Original Message-----
> From: [] On Behalf Of 
> Andrew Grieve
> Sent: Monday, June 23, 2014 9:42 PM
> To: dev
> Subject: Re: Contacts API, iOS
> 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 <> 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 <>
> > Sent: Saturday, June 21, 2014 12:09 PM
> > To:
> > 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.
> >

Carlos Santana
View raw message