Mirage fails when models are in sub-folders

Using 0.2.0-beta.8 ember g mirage-model admin/log

ember.debug.js:32127Error: Assertion Failed: Subdirectories under admin are not supported at new Error (native) at Error.EmberError (http://localhost:4200/assets/vendor.js:26056:21) at assert (http://localhost:4200/assets/vendor.js:15815:13) at Object.assert (http://localhost:4200/assets/vendor.js:25820:34) at http://localhost:4200/assets/vendor.js:117769:25 at Array.forEach (native) at exports.default (http://localhost:4200/assets/vendor.js:117761:8) at startMirage (http://localhost:4200/assets/client.js:415:66) at Object.initialize (http://localhost:4200/assets/client.js:406:9) at http://localhost:4200/assets/vendor.js:14823:23

[abrthel]

To work around this issue for now I’ve implemented the typeKeyForModel hook in my mirage application serializer.

import { JSONAPISerializer } from 'ember-cli-mirage'
import Ember from 'ember'
const { dasherize, pluralize } = Ember.String

export default JSONAPISerializer.extend({
  typeKeyForModel(model) {
    let typeKey = model.typeKey || model.modelName
    return dasherize(pluralize(typeKey))
  }
})

Then on each model I just place a typeKey attribute where I need to adjust the output type. For instance I have a model that lives in the folder models/references/faction and ember can find it if I create a mirage model like so

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

export default Model.extend({
  typeKey: 'references/faction'
})

[mrosenberg]

I’m writing some manual fixes now.

Mirage is awesome and the new ORM will be killer. Thanks for all your hard work on this.