npm paclages can be deprecated without releasing a new version.
Sent from my iPhone
> On 6. Jul 2020, at 12:45 AM, Norman Breau wrote:
>
> Ok so general consensus is that we should deprecate, but we must first
> release a version that to restrict
> the plugin from being installed on
Ok so general consensus is that we should deprecate, but we must first
release a version that to restrict
the plugin from being installed on cordova-ios platform. This is already
done and merged via
https://github.com/apache/cordova-plugin-wkwebview-engine/pull/158 so I
think all we need is a
Yeah, I think we can deprecate it since cordova-ios 6 works the same way by
default, but as Darryl said, we should do a last release with the engines
properly configured to not install in cordova-ios 6.
El El vie, 3 jul 2020 a las 20:04, Darryl Pogue
escribió:
> I don't know that we want to go
I don't know that we want to go as far as deprecating it just yet, but
we should definitely do a release that prevents it from being
installed with cordova-ios 6 (since it conflicts).
On Fri, Jul 3, 2020 at 10:50 AM Chris Brody wrote:
>
> It would definitely be nice if we don't have to support
It would definitely be nice if we don't have to support that plugin any
longer, and I think it would be good to archive it as well. My one comment
is that there should be a very clear guide for people who have to continue
using the same scheme due to data stored by the web view. A couple of
Hi team,
I believe previously we decided on a path to deprecate
cordova-plugin-wkwebview-engine, but I wanted
to make sure that is still our stance.
cordova-ios@6 supports both url schemes and the legacy file scheme,
effectively making the wkwebview engine plugin redundant. Now that
