status-im
/
realm-js
mirror of https://github.com/status-im/realm-js.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
realm-js/lib/.eslintrc

14 lines
161 B
Plaintext
Raw Normal View History

Initial concept of JS for Chrome debugging The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node). The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-02 05:56:47 +00:00
{
"env": {
"commonjs": true,
"browser": true,
Efficient React ListView for Realm collections This component is fully backwards compatible with the original React ListView, but is compatible with Realm Results and List objects to use their snapshot functionality along with more efficiently checking if each row should update.
2016-01-11 23:11:15 +00:00
"es6": true
Initial concept of JS for Chrome debugging The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node). The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-02 05:56:47 +00:00
},
Remove uses of for-of loops in RPC modules The React Native packager does not transform for-of loops, and minification step uses UglifyJS, which does not yet support ES6 syntax. Fixes #120
2015-11-06 00:10:52 +00:00
"ecmaFeatures": {
"forOf": false
},
Update RPC JS to use originalXMLHttpRequest React Native now leaves the original object accessible when it "polyfills" objects. So we check for that, but still have the previous logic in place in case they change their minds.
2015-10-21 06:59:02 +00:00
"globals": {
"global": true
Initial concept of JS for Chrome debugging The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node). The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-02 05:56:47 +00:00
}
}