Rename store and adapter for Ember Data compatibility

[nolaneo]

@intercom we're using both Ember Model and Ember Data in production. We're in the process of migrating fully to Ember Data. While that migration is happening, we have renamed the Ember Model store and data adapter to allow us to use both addons simultaneously as they conflict otherwise.

In this PR we've renamed store to emstore and data-adapter to em-data-adapter.

@ebryn This is a breaking change, but it might be something for you to consider. It opens a path for people to move to Ember Data without having to rewrite all their models at once. Let me know your thoughts. 🙂

[GavinJoyce]

This is a breaking change

@nolaneo perhaps you could outline the ways in which this is breaking so that we can consider what might be the best path forward?

[nolaneo]

In the current release of Ember Model, you create and query records directly through the store by using this.store.createRecord and this.store.find.

For example

let user = this.store.createRecord('user', {name: "Eoin"});
...
let user = this.store.find('user', 1).then(() => ...);

This clashes with Ember Data's usage of this.store.

With this proposed change, you would be required to rename any existing calls to the Ember Model store with the updated naming.

The above example would become

let user = this.emstore.createRecord('user', {name: "Eoin"});
...
let user = this.emstore.find('user', 1).then(() => ...);
...
// Which then allows us to do something like:
let emberDataModel = this.store.createRecord('my-ember-data-model', { ... });

[GavinJoyce]

Thanks.

If we'd like to avoid breaking compatibility, we could possibly make the name of the store configurable with a default of store and include instructions on how to enable ember-model and ember-data to work together.

Another option might be to run the ember-model initializer after the ember-data intializer and use a name of emstore if ember-data is present.

[darylalexjohnson]

First off, thanks @GavinJoyce Big thumbs up on this PR as a way to migrate off of ember-model to ember-data. We will be pushing this to a production environment in the coming weeks.

[bmac]

One breaking change that may not be obvious from this change is if a user is relying on Ember Route's to automatically find a record when the param follows the pattern <modelname>_id it won't work with Ember Model unless the store is the store property on the Route. See: https://github.com/emberjs/ember.js/blob/ef8f46e15d920dfbe008594a0177a9a2103f90ed/packages/ember-routing/lib/system/route.js#L1612-L1615.

Example:

Router.map(function() {
  this.route('photos', function(){
    this.route('edit', { path: '/:photo_id' });
  });
});

{{#link-to "photos.edit" 1}}

// photos.edit route
export default Ember.Route.extend({
  // This method does not need to be defined since Ember will do this automagically.
  // In practice relying on this behavior is outdated but it still may be used by some older Ember Apps
  model(params) {
    return this.store.find('photo', params.photo_id)
  }
})

[bmac]

Not to discourage this change just for information purposes, as of 2.0.0 Ember Data no longer registers anything on store:main or store:application instead Ember Data registers its store to service:store.

[GavinJoyce]

Closing in favour of #474. I'm going to see if we can land this soon