> > And I would also like to remove the "protective" engine all plugins have
> that points the next major version to cordova >= 100
>
> +1. I never really understood the rationale behind this. I think it's
> safe to assume that a next plugin major will continue to support the
> cordova cli that
on this.
On 2020-07-14 9:09 a.m., julio cesar sanchez wrote:
Historically we have only used/updated plugin engines when a certain
cordova-cli/android/ios version was needed because of a new
feature required by the plugin.
Nowadays, most plugins still (technically) support
old cordova-cli/a