Inspired by Ember Data, JSData is the model layer you've been craving. It consists of a convenient framework-agnostic, in-memory store for managing your data, which uses adapters to communicate with various persistence layers.
The most commonly used adapter is the http adapter, which is perfect for communicating with your RESTful backend. localStorage, localForage, firebase and other adapters are already available. On the server you could hook up to the SQL adapter (Postgres/MySQL/MariaDB/SQLite3) and add in the Redis adapter as a caching layer for your read endpoints. More adapters are coming, and you're free to implement your own. See Adapters.
Unlike some libraries, JSData does not require the use of getters and setters,
and doesn't decorate your data with a bunch of cruft. JSData's internal change
detection (via observe-js or Object.observe in supporting browsers)
allows for powerful use cases and an easy avenue for implementing your own
3-way data-binding.
Supporting relations, computed properties, support for Node and the Browser, model lifecycle control and a slew of other features, JSData is the tool for giving your data the respect it deserves.
Written in ES6 and built for modern web development, JSData will save you thousands of lines of code and make you cooler.
Support is handled via the Slack channel or the Mailing List.
JSData is getting popular and becoming a lot of work for me. I could use help with tests, documentation, demos/examples, and adapters. Contact me if you wan to help! jason dot dobry at gmail dot com
JSData requires the presence of the ES6-spec (ES2015) Promise constructor in
the global environment. In the browser, window.Promise must be available. In
Node, global.Promise must be available. Here is a handy library for
polyfilling: https://github.com/jakearchibald/es6-promise.
If you can't polyfill the environment, then configure JSData to use a specific
Promise constructor directly: JSData.DSUtils.Promise = MyPromiseLib;.
This direct configuration method is useful for telling JSData to use the
Bluebird library or Angular's $q, etc.
bower install --save js-data js-data-http or npm install --save js-data js-data-http.
Load js-data-http.js after js-data.js. See installation instructions
for making js-data part of your r.js/browserify/webpack build.
// you can also require "js-data" if you're using AMD/CommonJS
// e.g. var JSData = require('js-data'); var DSHttpAdapter = require('js-data-http');
var store = new JSData.DS();
// register and use http by default for async operations
store.registerAdapter('http', new DSHttpAdapter(), { default: true });
// simplest model definition, just pass the name instead of an options hash
// this is the same as "store.defineResource({ name: 'user' })"
var User = store.defineResource('user');
// Usually you'll define a resource by passing options
var Comment = store.defineResource({
name: 'comment',
relations: {
belongsTo: {
user: {
// "join" field, name of field on a comment
// that is the primary key of the parent user
localKey: 'userId',
// name of the field on the comment where the
// parent user will be attached to the comment
// by js-data
localField: 'user'
}
}
}
});
var user;
// Example CRUD operations with default configuration
// See http://www.js-data.io/docs/dsfind
User.find(1)
.then(function (_user) {
_user; // { id: 1, name: 'John' }
// See http://www.js-data.io/docs/dsis
User.is(_user); // true
Comment.is(_user); // false
// The user is in the store now
// See http://www.js-data.io/docs/dsget
User.get(_user.id); // { id: 1, name: 'John' }
user = _user;
// No need for another GET request, will resolve immediately
// See http://www.js-data.io/docs/dsfind
return User.find(1);
})
.then(function (_user) {
user === _user; // true
// PUT /user/1 {name:"Johnny"}
// See http://www.js-data.io/docs/dsupdate
return User.update(user.id, { name: 'Johnny' });
})
.then(function (_user) {
// identity mapping at play
user === _user; // true
user === User.get(_user.id); // true
user; // { id: 1, name: 'Johnny' }
user.name = 'Billy';
// PUT /user/1 {id:1,name:"Billy"}
// See http://www.js-data.io/docs/dssave
return User.save(1);
})
.then(function (_user) {
// identity mapping at play
user === _user; // true
user === User.get(_user.id); // true
user; // { id: 1, name: 'Johnny' }
// DELETE /user/1
// See http://www.js-data.io/docs/dsdestroy
return User.destroy(1);
})
.then(function () {
// The user has also been removed from the in-memory store
User.get(1); // undefined
});All your data are belong to you...
- Getting Started with js-data
- Resources/Models
- Working with the Data Store
- Adapters
- Model Lifecycle
- Custom Instance Behavior
- Computed Properties
- Relations
- Schemata & Validation
- JSData on the server
- Angular + JSData
- FAQ
See an issue with or have a suggestion for the documentation? You can suggest edits right on the documentation pages! (There's a link at the top right of each page.)
- DS
- Configuration Options
- DSFirebaseAdapter
- DSHttpAdapter
- DSLevelUpAdapter
- DSLocalForageAdapter
- DSLocalStorageAdapter
- DSMongoDBAdapter
- DSNeDBAdapter
- DSRedisAdapter
- DSRethinkDBAdapter
- DSSqlAdapter
- js-data-schema
- Slack Channel
- Better than IRC!
- Announcements
- Mailing List - Ask your questions!
- Issues - Found a bug? Feature request? Submit an issue!
- GitHub - View the source code for JSData.
- Contributing Guide
First, support is handled via the Slack Channel and the Mailing List. Ask your questions there.
When submitting issues on GitHub, please include as much detail as possible to make debugging quick and easy.
- good - Your versions of Angular, JSData, etc, relevant console logs/error, code examples that revealed the issue
- better - A plnkr, fiddle, or bin that demonstrates the issue
- best - A Pull Request that fixes the issue, including test coverage for the issue and the fix
- Contribute to the issue/discussion that is the reason you'll be developing in the first place
- Fork js-data
git clone git@github.com:<you>/js-data.gitcd js-data; npm install; bower install;- Write your code, including relevant documentation and tests
- Run
npm test(build and test) - Your code will be linted and checked for formatting, the tests will be run
- The
dist/folder & files will be generated, do NOT commitdist/*! They will be committed when a release is cut. - Submit your PR and we'll review!
- Thanks!
The MIT License (MIT)
Copyright (c) 2014-2015 Jason Dobry
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.