cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <>
Subject Re: cordova-plugin-whitelist ios issue
Date Wed, 30 Sep 2015 19:23:17 GMT
That's a bad argument Carlos and you know it. No one will see the
warning unless they add the firefoxos platform, and if they added it,
it is relevant to them. This is a valid warning.

Plugins are in cross-platform territory and this will happen, let's
not skirt around it. We can hide now by "fixing the source" but that's
just avoiding it. The problem here is not the warning, but informing
the user properly. Like I said, we can add an <info> tag.

On Wed, Sep 30, 2015 at 8:48 AM, Carlos Santana <> wrote:
> So this mean I can add this engine tag today to the whitelist plugin with
> some code specific to firefoxos?
>  <engine name="cordova-firefoxos" version=">=4.0.0-dev" />
> I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on npm
> but is very useful to give users the warning now.
> This will avoid the user from upgrading the plugin ever in the future when c
> ordova-firefoxos@4.0.0 is published to npm, I might get c
> ordova-firefoxos@4.0.0 around december or longer  so I don't think it will
> be a problem for them to see the warning until then.
> If everyone is OK I will put this code today? this will avoid user from
> having to upgrade the plugin in the future :-p
> This is the point I want to make, and guess email communication is not
> being our friend to express my point of view.
> Will those interested on this topic up for a quick Hangout? Simon, Shaz,
> Nikhil
> On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald <>
> wrote:
>> -1 to this proposal IMHO
>> Warnings are useful. If someone sees this and is confused as to why there
>> is a new whitelist plugin then looks into it some more detail that will be
>> beneficial. I think the warning should be more explicit. Put an info tag
>> into the plugin.xml for the whitelist linking to the docs and what the
>> upcoming change is in cordova-ios 4.0.0. That way people will be "less"
>> surprised that they need to install this plugin in the future.
>> Simon Mac Donald
>> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams <>
>> wrote:
>> > This.
>> >
>> > +1
>> >
>> >
>> > On 30 September 2015 at 12:31:29, Carlos Santana (
>> > wrote:
>> >
>> > In summary I proposed that we update the plugin with a version that only
>> > contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version that
>> > contains the ios code and contains engine tag stating that it needs
>> > minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 1.x it
>> > contains android only, branch 2.x contains both android and ios.
>> >

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message