`Relation is defined but the resource is not` Error about js-data HOT 4 CLOSED

Yes, it's a quirk of Angular's dependency injection. The DI system is lazy in that it waits to execute the setup code for the dependency until the dependency is actually needed. So if you don't actually inject Ad or Classified before that route resolve is executed, then those resources actually haven't yet been registered with the data store.

One way I get around it is the inject all my resources into the .run function of my angular app.

from js-data.

@demisx, this is how all of my factories look:

.factory('Classified', function(DS) {
  return DS.defineResource({
    name: 'classified',
    endpoint: '/classifieds',
    relations: {
      hasMany: {
        ad: {
          foreignKey: 'adId',
          localField: 'ad'
        }
      }
    }
  });
}).run(function(Classified) {}); // this line

That way the file that creates it also makes sure that it runs :-)

from js-data.

@kentcdodds Aha! I like that. Thank you Kent. Would be great to capture this in the docs as well.

from js-data.

@kentcdodds Nice tip!

With strictdi = true and (ES6), I use .run(['Classified', () => {}]

from js-data.