Multiple data stores and model namespacing

@EmberKing wrote:

Greetings,

Most similar questions are about having the same model connect to different backend apis.

What I want to achieve is to have two totally different models with different properties but with the same name connect to different apis. I tried different approaches, but I assume the only real way (and logical) is to have multiple data stores. At the same time, I’ve found no documentation on multiple stores and even found information that says, multiple stores should not be used in Ember (https://stackoverflow.com/questions/14321712/can-i-specify-a-store-on-a-ember-js-model). This was back in the days when name spacing was done differently.

I have created an addon with just the models, adapters, serializers, and a new store service called “core-store”. Each entity extends a “core” adapter and serializer so that the addon doesn’t use the main project’s “application” adapter and serializer.

The addon’s “core-store” service:

import DS from 'ember-data';

export default DS.Store.extend({
    adapter: 'core'
});

The main project’s route that queries the “core-store”

import Route from '@ember/routing/route';
import { inject as service } from '@ember/service';

export default Route.extend({
    coreStore: service(),

    model(params) {
        let workplace = this.get('coreStore').findRecord('workplace', params.master_id);
        return workplace;
    }
});

The main project contains several models that have the same name as the addon’s models. The workplace model has relationships to these. When it builds the model instances, it chooses to use the main project’s instead of the addon’s.

I can give more info if need be. I’ve tried many approaches, but I have yet to try the ember addon for multiple stores: https://github.com/jonesetc/ember-cli-multi-store-service. Going to give it a try while I wait for replies.

Please do let me know what the best approach here is. I’m surprised there isn’t much info

Posts: 1

Participants: 1

Read full topic