Do not call adapter.deleteRecord for a record that is already saved and deleted.
Remove DS.AttributeChange.
Add an example of sending cookie information in the header and updated confusing reopen example.
Update error messages from push and update

Error messages now include model type for ease of debugging
allow saving records from invalid state

tests by @alexspeller
Use `package.json` as gem version
Fix to update ember-data version

Now, ember-data is versioned as 1.0.0-beta.8+canary.
[DOC] Fix jsdoc for `Serializer#extractSingle`

Now the argument `requestType` is unused.
This commit is the part of be797b992 .
Merge pull request #1930 from tricknotes/jsdoc

[DOC] Fix jsdoc for `Serializer#extractSingle`
Put the initialization docs back with the initializers
Update the docs on pushPayload to clarify how model is used
Merge pull request #1932 from mixonic/push-payload

Push payload
Merge pull request #1889 from tchak/invalid-save

Allow saving records from invalid state
Merge pull request #1905 from tricknotes/use-package.json-as-gem-version

Use package.json as gem version
Use SVG for the Travis badge in the README
Merge pull request #1935 from MaxGabriel/patch-1

Use SVG for the Travis badge in the README
[BUGFIX] Normalize typeKeys to always be camelCase

typeKeys must have a strong formatting convention, since they are used
for comparison in several spots of the code. Prior to this commit:

  * The container's normalized version of the factory name was set to
    the typeKey. This leaked the container concerns about name
    formatting up to Ember-Data, and to the user's interaction with
    API calls like `find('some-module')`
  * The typeKey property of a model class was allowed to pass into the
    code without normalization.

In general, for a developer to know which to pick of `find('some-car')`,
`find('someCar')` or `find('some_cars')` they had to understand which
resolver their container was using. This demonstrates a bad coupling,
and makes documenting Ember-Data exceedingly hard (we should not need to
mention a caveat about picking a resolver).

This commit normalizes typeKeys to always be camelCase, both those
returned by `typeForRoot` (for which the documentation has been
improved) and for those set on factories by `modelFor`.

From here on, `find('someCar')` should be considered the standard format
for multi-word model names.
normalizePayload only gets the payload

normalizePayload has been living a lie. It claims to be passed the model
type when called, but in often does not receive this argument (null is
passed instead). This only serves to confuse the use-case for
normalizePayload, and encourage its use when overriding an extraction
helper is actually the right choice.

This tradeoff, dropping the argument of type in all cases, means
normalizePayload can still be run over data added with pushPayload.
pushPayload knows nothing of which model is being pushed, and thus
cannot provide the type reliably.
Add a base fiddle for mocked data requests with Ember Data
Removed unused resolver from ManyArray.fetch