I mostly agree with Braden, except would like to see a top-level CLI
command to do that automatically. `cordova upgrade` could re-add installed
platforms and plugins in a temporary location, and swap it into your
project root only if it completes successfully, and also moving your old
version into
Ian wrote:
>I'm not sure what you mean by "misusing" the exec API. Do you mean that
>the
>JS side of the plugin was using the exec bridge in some undocumented way?
Exec is an async api, but due to bugs in the underlying BlackBerry 10, the
implementation of blackberry¹s exec function was sync.
Som
Hi Josh,
I'm not sure what you mean by "misusing" the exec API. Do you mean that the
JS side of the plugin was using the exec bridge in some undocumented way?
Or that the bridge is being used correctly, but the native side is
returning objects that the javascript side isn't expecting?
On Thu, F
I continue to feel that the right approach to platform updates is mostly to
keep making platforms/ a build artifact, and largely plugins/ too.
I feel that the right thing for an app developer to do for updating
platforms would be to backup the entire project, empty out platforms/ and
plugins/, and
So, we discovered that a number of plugins are misusing an API in our platform
(exec). We changed the implementation, and this broke the plug-ins which were
expecting different but not promised behavior.
There's a cordova-cli platform update command, which is supposed to update your
platform, b
