Infered ember data models don't respect the inverse arg

[lougreenwood]

Bug?

When an ED relationship is one-way, it should be marked as inverse: null, this is essential for mirage models, due to #996.

However, when allowing Mirage to infer the model from ED (so not explicitly defining a mirage model), the inverse: null does not seem to brought along, so the above problem is encountered and the only solution is to define a mirage model.

However, this is troublesome, since this then adds a maintenance burden of keeping the real ED models and mirage models in sync.

[lougreenwood]

Some research for fixing:

• Looks like ember-cli-mirage should pick up inverse:null option here and pass to mirageJs

  • ember-cli-mirage/addon/ember-data.js

    Line 77 in 324a032

    model.eachRelationship((name, r) => {

• mirageJs receives the opts for belongsTo here:
  • https://github.com/miragejs/miragejs/blob/b965b8a058523dac0d6ab4792826887154e25368/lib/orm/associations/association.js#L78
• However, I assume that mirageJs doesn't set null inverse here since it ignore null value for inverse, so no inverse is detected, so the inverse option is skipped in something like model.hasInverseFor
  • https://github.com/miragejs/miragejs/blob/b965b8a058523dac0d6ab4792826887154e25368/lib/orm/associations/belongs-to.js#L203