I'm in favor of ES6 classes.
But that doesn't mean that everything that _can_ be written with classes
should. Pick the right tool for the job.
While you can achieve the same object structure by just extending the
prototype, classes have the benefit of keeping related code parts close
to each
I'm definitely in favour of using classes. Personally I find them easier to
read and write. We are already using them in at least one place, the
ProjectBuilder in cordova-android.[1] This came about from a refactor I did a
few months ago, and since we dropped support for Node 6, it made sense to
I just finished revising my PRs regarding the deprecation and
archiving of repositories. Finishing this is needed to actually be
able to go ahead and vote on the archival of the first repositories.
1. First one is a general "Deprecation and Archiving Policy" that
would be available on our website
Another PR that I polished a bit and is ready for feedback and
reviews: "Create a Minimal Reproduction Repository or Sample"
PR: https://github.com/apache/cordova-contribute/pull/6
Preview:
https://github.com/apache/cordova-contribute/blob/0a582edd0857353ff8790cbe5e6560bbcb72e7a7/create-reproduct
Nightly build #927 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/927/consoleFull
-
Jenkins for Apache Cordova
-
