realm-js/lib/lists.js

'use strict';

let types = require('./types');
let util = require('./util');

module.exports = {
    create,
};

class List {}

util.createMethods(List.prototype, types.LIST, [
    'pop',
    'shift',
    'push',
    'unshift',
    'splice',
], true);

function create(realmId, info) {
    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-01 22:56:47 -07:00			`'use strict';`

Generalize calling methods through the RPC 2015-10-19 12:06:47 -07:00			`let types = require('./types');`
JS implementation for Results from RPC 2015-10-07 17:08:19 -07:00			`let 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-01 22:56:47 -07:00
Generalize calling methods through the RPC 2015-10-19 12:06:47 -07: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-01 22:56:47 -07:00
Generalize calling methods through the RPC 2015-10-19 12:06:47 -07: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-01 22:56:47 -07:00
Generalize calling methods through the RPC 2015-10-19 12:06:47 -07:00			`util.createMethods(List.prototype, types.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-01 22:56:47 -07:00			`'pop',`
			`'shift',`
			`'push',`
			`'unshift',`
			`'splice',`
Generalize calling methods through the RPC 2015-10-19 12:06:47 -07: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-01 22:56:47 -07:00
			`function create(realmId, info) {`
Generalize getting/setting properties through RPC 2015-10-19 15:26:42 -07: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-01 22:56:47 -07:00			`}`