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/lists.js

27 lines
466 B
JavaScript
Raw Normal View History

Add beta licenses to Chrome JS modules
2015-10-28 17:37:17 +00:00
/* Copyright 2015 Realm Inc - All Rights Reserved
* Proprietary and Confidential
*/
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
'use strict';
Sprinkle some const inside ES6 JS code React Native 0.13.0 fixes the bug we experienced by using const.
2015-10-21 20:25:12 +00:00
const constants = require('./constants');
const util = require('./util');
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
Generalize calling methods through the RPC
2015-10-19 19:06:47 +00:00
module.exports = {
create,
};
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
Generalize calling methods through the RPC
2015-10-19 19:06:47 +00:00
class List {}
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
Move all constants into a single JS file
2015-10-19 23:19:43 +00:00
util.createMethods(List.prototype, constants.propTypes.LIST, [
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
'pop',
'shift',
'push',
'unshift',
'splice',
Generalize calling methods through the RPC
2015-10-19 19:06:47 +00:00
], 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
function create(realmId, info) {
Make List objects work with Object.keys in Chrome Rather than using Object.preventExtensions to throw exceptions when setting any out-of-bounds index, we must instead compromise by only throwing for the common cases, which are -1 and list.length. Having Object.keys() support is essential for List to work with React Native ListViewDataSource. Resolves #80
2015-10-21 20:09:51 +00:00
return util.createList(List.prototype, realmId, info, 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
}