Include test to show error introduced with last embedded changes
AdapterPopulatedRecordArray triggers `didLoad` event at the end of the runLoooop

- Fixed reported integration tests
- Add Em.run to some tests which became invalid with this change
This allow to define integer ids in the fixtures, as well as integers

correct test title
Add a space in the assertion message
Merge pull request #618 from marktheunissen/minor-type-in-assertion

Add a space in the assertion message
Merge pull request #605 from sly7-7/fixture-adapter-coerce-ids

Allow to define integer ids in the fixtures, as well as string
Merge pull request #580 from ppcano/load-async-error

Trigger didLoad event in the `AdapterPopulatedRecordArray` at the end of the runloop
Demonstrate unwanted record sharing.

By adding a pingbacks relationship and not modifying it in any test, we
should end up with an empty array in all serialized Posts, i.e.

    {
        "post": {
            "comments": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "pingbacks": [],
            "title": "A New MVC Framework in Under 100 Lines of Code"
        }
    }

However, what we get is

    {
        "post": {
            "comments": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "pingbacks": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "title": "A New MVC Framework in Under 100 Lines of Code"
        }
    }
Consider relationship for embedded hasMany records.

When serializing a relationship, the previous algorithm serialized all
records in _all_ has-many relationships, not just all records for the
specified relationship.
Only serialize has-manys that are embedded
Using FixtureAdapter, ids must be defined in the FIXTURES
improve error message
Merge pull request #624 from sly7-7/fixtures-must-have-ids

Fixtures must have ids
The owner record is now an argument passed to findMany on the adapter

While writing an adapter for my django backend I was unable to
build a valid url for my hasMany relationships because the owner
was not easily accessible. Going forward the owner will now be an
argument available for custom adapters like the one I ended up writing.

example of how my REST api would lookup hasMany relationships:

If I have a person with many occupations I would look them up like so

/people/1/occupations/

Notice the id 1 above is actually the owner of the occupations (not a
occupation id from the ids array that is passed into findMany)

Instead of passing each id like the built in RESTAdapter the url above
just expects the owner will know how to find each occupation
Fix active_model_serializer link

Repo was moved to rails-api organization
Merge pull request #625 from toranb/master

The owner record is now an argument passed to findMany on the adapter
Fix typo in store error message
Merge pull request #631 from bobbus/fix-store-error-typo

Fix typo in store.findMany error message
Merge pull request #627 from strzalek/patch-1

Fix active_model_serializer link
Extract embedded `belongsTo` records properly

`sideload` won't consider relationships/embedded records, by using
`extractRecordRepresentation` we'll recurse into the record (similarly
to `extractEmbeddedHasMany`).