Include hasMany with fixtures does not seem to work

I have something similar to:

mirage/models/user.js:

import { Model, hasMany } from 'ember-cli-mirage'

export default Model.extend({
  comments: hasMany('text')
})

mirage/models/text.js:

import { Model, belongsTo } from 'ember-cli-mirage'

export default Model.extend({
  author: belongsTo('user')
})

mirage/fixtures/user.js:

export default [
  { id: 1, username: 'topaxi' }
]

mirage/fixtures/texts.js:

export default [
  { id: 1, content: 'foo', authorId: 1 },
  { id: 2, content: 'bar', authorId: 1 },
  { id: 3, content: 'baz', authorId: 1 }
]

mirage/scenarios/default.js:

export default (server) => {
  server.loadFixtures('users')
  server.loadFixtures('texts')
}

mirage/config.js:

export default () => {
  this.namespace = 'api/v1'

  this.get('/v1/users')
}

Now if I’m requesting /api/v1/users/1?include=comments, I will only get the user without any comments/texts included. I’m not sure if I’m doing something wrong. Should I specify the one-to-many relationship only once? Do the one-to-many includes only work if I create the models / objects by hand?

[topaxi]

It now works with ember-cli-mirage#master, thanks!

[samselikoff]

This is sort of a bug, sorry about the trouble it caused. It’s because hasMany tries to ensure there’s a foreign key on the child model, if it doesn’t exist. Because the fk is a named foreign key in this case, your child model ends up with two fks.

The solution is to name the inverse. Add this to your user model:

comments: hasMany('text', {inverseOf: 'author'})

and everything should work. I’ll open a new issue to improve this in the future. Thanks for reporting this!