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 release.
To get the deprecation notice on NPM readme, we'd also need a release.
Does this mean we need two different releases?
I'd be more than happy to take the initiative to start the release
process, but I don't have a mac, so I won't be able to run the native
unit tests, locally. This isn't exactly blocking, but I'm not sure if
there is anything else in this repo that would require a mac for
publishing. I also don't have npm publishing rights.
On 2020-07-03 3:43 p.m., julio cesar sanchez wrote:
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<dvpdin...@gmail.com>
escribió:
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<chris.br...@gmail.com> wrote:
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
off-topic items that I think are related:
I think we should recommend that people consider using native plugins
such
as cordova-plugin-file, SQLite, or something similar for storing
important
data.. I have seen quite a few things such as local storage deleting
data,
IndexedDB eviction, and other things going wrong to trust the WebView to
not lose data.
I think we should deprecate and archive some other plugins in the near
future, due to the support burden, as I proposed in:
https://github.com/apache/cordova/issues/185
On Fri, Jul 3, 2020 at 1:28 PM Norman Breau<nor...@normanbreau.com>
wrote:
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
cordova-ios@6 is released, I feel like it's time to formally deprecate
the wkwebview plugin according to our Deprecation Policy[1]
With that being said, I'm not sure if we also want to archive this
repository. According to the policy, we should archive if:
"A deprecated repository might also be archived if we don't intend to
provide support of any kind (Issues, Pull Requests, Releases) for this
component any more."
I feel like this is probably our intention as I think all maintenance
will now be done in cordova-ios going forward, but I want to gather
some
thoughts on this.
[1]https://cordova.apache.org/deprecation_policy.html
Cheers,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail:dev-unsubscr...@cordova.apache.org
For additional commands, e-mail:dev-h...@cordova.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:dev-unsubscr...@cordova.apache.org
For additional commands, e-mail:dev-h...@cordova.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
