Re: [aerogear-dev] javascript api sync
On Tue, Nov 19, 2013 at 10:21 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?
yes, I think updating the Cordova bits makes sense.
Quote from yesterdays team meeting:
<quote>
15:22:50 <qmx> #info qmx proposes to freeze this friday (as an exception to
android), freeze this friday, release next week, announce after the holiday"
</quote>
So the freeze is this week, and IMO that's perfectly fine to update it.
That said, but I think the only question I really have is why this update
to reflect the 'new' API was not addressed already last week.
Greetings,
Matthias
Cheers,
Erik Jan
p.s.
have a look at the differences:
current javascript api
https://github.com/aerogear/aerogear-js/blob/master/tests/unit/crypto/aer...
current cordova api
https://github.com/edewit/aerogear.org/blob/f2fe8a48b2f9d9c581e62292abeaf...
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Attachments:
- attachment.html (text/html — 3.5 KB)