<commit_before># Ember JSON API Resources

An [Ember CLI] Addon… a lightweight solution for data persistence in an [Ember.js]
application following the [JSON API] 1.0 specification (your anti-bikeshedding
weapon for API development).

For example code see the [tests/dummy](tests/dummy) app in this repo.

This solution uses the [Fetch API] instead of XMLHttpRequest (
see [Introduction to fetch()]).

URL's are first class in the JSON API 1.0 specification and first class
in the [Ember.js] Router. Why not make them first class in your persistence
solution too? Now you can with the [ember-jsonapi-resources] addon.

This addon was inspired by finding the simple path to shipping an application
implementing spec by using the [JSONAPI::Resources] gem, to production.

Whether you adopt the JSON API 1.0 spec, or not; this addon is a template for
creating a data persitence solution for your [Ember.js] application that models
the domain of your API server. The addon code is rather concise, borrow at will.


[Introduction to fetch()]: http://updates.html5rocks.com/2015/03/introduction-to-fetch
[Fetch API]: https://fetch.spec.whatwg.org
[JSON API]: http://jsonapi.org
[Ember CLI]: http://www.ember-cli.com
[ember-jsonapi-resources]: https://github.com/pixelhandler/ember-jsonapi-resources
[JSONAPI::Resources]: https://github.com/cerebris/jsonapi-resources
[Ember.js]: http://emberjs.com


## Installation

To consume this addon in an Ember CLI application:

    ember install ember-jsonapi-resources


## Resource Generator
<commit_msg>Remove incorrect apostrophe in URL's.<commit_after># Ember JSON API Resources

An [Ember CLI] Addon… a lightweight solution for data persistence in an [Ember.js]
application following the [JSON API] 1.0 specification (your anti-bikeshedding
weapon for API development).

For example code see the [tests/dummy](tests/dummy) app in this repo.

This solution uses the [Fetch API] instead of XMLHttpRequest (
see [Introduction to fetch()]).

URLs are first class in the JSON API 1.0 specification and first class
in the [Ember.js] Router. Why not make them first class in your persistence
solution too? Now you can with the [ember-jsonapi-resources] addon.

This addon was inspired by finding the simple path to shipping an application
implementing spec by using the [JSONAPI::Resources] gem, to production.

Whether you adopt the JSON API 1.0 spec, or not; this addon is a template for
creating a data persitence solution for your [Ember.js] application that models
the domain of your API server. The addon code is rather concise, borrow at will.


[Introduction to fetch()]: http://updates.html5rocks.com/2015/03/introduction-to-fetch
[Fetch API]: https://fetch.spec.whatwg.org
[JSON API]: http://jsonapi.org
[Ember CLI]: http://www.ember-cli.com
[ember-jsonapi-resources]: https://github.com/pixelhandler/ember-jsonapi-resources
[JSONAPI::Resources]: https://github.com/cerebris/jsonapi-resources
[Ember.js]: http://emberjs.com


## Installation

To consume this addon in an Ember CLI application:

    ember install ember-jsonapi-resources


## Resource Generator

{'fraction_non_alphanumeric': 0.09049919484702093, 'fraction_numerical': 0.008373590982286634, 'mean_word_length': 4.688644688644689, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '156905', 'n_tokens_mistral': 924, 'n_tokens_neox': 872, 'n_words': 378}