This clarifies whether we can even *use* ReactJS, the answer is "No":
https://issues.apache.org/jira/browse/LEGAL-319
On Sat, Jul 15, 2017 at 11:19 AM, Shazron wrote:
> i.e. React
>
> See https://s.apache.org/upmi
> And https://www.apache.org/legal/resolved.html
>
> Note that even though we "use
i.e. React
See https://s.apache.org/upmi
And https://www.apache.org/legal/resolved.html
Note that even though we "use" React in plugins.cordova.io (through an npm
dependency), and not include it in our repo, I suggest we remove its usage
and use Preact, a drop-in replacement (untested).
I filed:
Github user shazron commented on the issue:
https://github.com/apache/cordova-ios/pull/326
Not sure yet why the appveyor CI (Windows) is failing some tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user shazron commented on the issue:
https://github.com/apache/cordova-ios/pull/326
We had to pull in new code for the new linter using eslint. Consequently,
some files have changed. Can you try rebasing, then running npm run eslint to
make sure it's all kosher
---
If your pr
Github user shazron commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/168
This patch (pun, I know) needs a README update for `httpMethod` as well, to
be complete.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user shazron commented on the issue:
https://github.com/apache/cordova-ios/pull/324
We had to pull in new code for the new linter using eslint. Consequently,
some files have changed. Can you try rebasing, then running `npm run eslint` to
make sure it's all kosher
---
If your
