Just to be very accurate, the API interface has changed 11 days ago
(
https://github.com/aerogear/aerogear-js/pull/78) and the full integration with the
datamanager was 6 days ago (
https://github.com/aerogear/aerogear-js/pull/82) on time with
the freezing dates.
I can’t be very wrong but I don’t see reason to have an outdated documentation at our
site, as well the code. Once Cordova depends on several platforms, we should improve our
communication on the next release.
On November 19, 2013 at 7:21:14 AM, Erik Jan de Wit (edewit(a)redhat.com) wrote:
Hi,
Last tuesday the PR for the new javascript crypto api landed, because I developed the
crypto cordova plugin based on the 'old' api there is now a discrepancy between
the 'current' javascript crypto api and the cordova one. We could change that this
week as there aren't that many people that use the crypto cordova plugin, but we have
frozen so what is the point of a freeze when we change things regardless?
Anyway I think we could still change this what do you think?
--
abstractj