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
>
>

Reply via email to