shakakira / data-1 Goto Github PK

Ember Data is a library for loading data from a persistence layer (such as a JSON API), mapping this data to a set of models within your client application, updating those models, then saving the changes back to a persistence layer. It provides many of the facilities you'd find in server-side ORMs like ActiveRecord, but is designed specifically for the unique environment of JavaScript in the browser.

This is definitely alpha-quality. The basics work, but there are for sure edge cases that are not yet handled. Please report any bugs or feature requests, and pull requests are always welcome.

Yes.

No. The API should not be considered stable until 1.0. Breaking changes, indexed by date, are listed in BREAKING_CHANGES.md.

A guide is provided on the Ember.js site that is accurate as of revision 11.

Currently you must build ember-data.js yourself. Clone the repository, run bundle then rake dist. You'll find ember-data.js in the dist directory.

• Handle error states
• Better built-in attributes
• Editing "forked" records
• Out-of-the-box support for Rails apps that follow the active_model_serializers gem's conventions.
• Handle partially-loaded records

1. Install Ruby 1.9.2+. There are many resources on the web can help; one of the best is rvm.

2. Install Bundler: gem install bundler

3. Run bundle inside the project root to install the gem dependencies.

1. To start the development server, run rackup.

2. Then visit: http://localhost:9292/?package=PACKAGE_NAME. Replace PACKAGE_NAME with the name of the package you want to run. For example:

• Ember.js Data

To run multiple packages, you can separate them with commas. You can run all the tests using the all package:

http://localhost:9292/?package=all

You can also pass jquery=VERSION in the test URL to test different versions of jQuery. Default is 1.9.0.

1. Install phantomjs from http://phantomjs.org

2. Run rake test to run a basic test suite or run rake test[all] to run a more comprehensive suite.

3. (Mac OS X Only) Run rake autotest to automatically re-run tests when any files are changed.