js-data

js-data

Inspired by Ember Data, JSData is the model layer you've been craving. It consists of a convenient in-memory cache for managing your data, and several adapters for communicating with various persistence layers.

By default JSData uses the http adapter, which is perfect for communicating with your RESTful backend. It also includes a localStorage adapter. More adapters are coming, and you're free to implement your own.

Unlike Backbone and Ember Models, JSData does not require the use of getters and setters, and doesn't wrap your data with custom classes if you don't want it to. JSData's internal dirty-checking (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, model lifecycle control and a slew of other features, JSData is the tool for giving your data the respect it deserves.

All your data are belong to you...

Latest Release: pending master: 0.0.1

JSData is pre-alpha. The API is subject to change, though the current api is well tested.

If you want to use JSData, keep a close eye on the changelog. 1.0.0 will introduce strict semver (until then, minor number is bumped for breaking changes).

Documentation

http://js-data.io

Project Status

Branch	Master
Bower
NPM
Build Status
Code Climate
Dependency Status
Coverage

Quick Start

bower install --save js-data or npm install --save js-data.

var dataStore = new JSData.DS();

var User = dataStore.defineResource('user');

User.find(1).then(function (user) {
  user; // { id: 1, name: 'John' }
});

API

• Overview
• DS
• DSHttpAdapter
• DSLocalStorageAdapter

Changelog

CHANGELOG.md

Version Migration

TRANSITION.md

Community

• Mailing List - Ask your questions!
• Issues - Found a bug? Feature request? Submit an issue!
• GitHub - View the source code for js-data.
• Contributing Guide

Contributing

First, feel free to contact me with questions. Mailing List. Issues.

1. Contribute to the issue that is the reason you'll be developing in the first place
2. Fork js-data
3. git clone https://github.com/<you>/js-data.git
4. cd js-data; npm install; bower install;
5. grunt go (builds and starts a watch)
6. (in another terminal) grunt karma:dev (runs the tests)
7. Write your code, including relevant documentation and tests
8. Submit a PR and we'll review

License

Copyright (C) 2014 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.