Understanding polymorphism about data

[Jopie01]

OK, digged a bit deeper through the code and specifically https://github.com/emberjs/data/blob/5a48f52a08587e59cb529575577880daf678ae00/packages/store/src/-types/q/schema-service.ts the last portion. As it turns out I have the polymorphic: true at the wrong level. It should be in the options

menu model:
{
  action: {
    name: 'action',
    kind: 'belongsTo',
    options: {
        polymorphic: true,
        async: true,
        inverse: null
    }
  }
}

Seems like I don't have to specify a type because with this I'm able to push data into the store and then I can happily request it from the store without errors. The only extra thing I have to do is to make sure the models exists when data is pushed, so first fetch the model before pushing into the store.

[runspired]

For inverse: null yes, there is nothing additionally needed though you are missing the abstract type and should make sure you include it.

{
  action: {
    name: 'action',
    kind: 'belongsTo',
+   type: 'action', // I'm guessing here that the abstract type is also "action"
    options: {
        polymorphic: true,
        async: true,
        inverse: null
    }
  }
}

For inverse: <some-prop> the corresponding field on the other record must specify the abstract type. So for instance, assume menu said this:

{
  action: {
    name: 'action',
    kind: 'belongsTo',
+   type: 'action',
    options: {
        polymorphic: true,
        async: true,
+       inverse: 'lists'
    }
  }
}

Then any record that satisfies "action" must have the below field def:

// "add-item" action
{
  lists: {
    name: 'lists',
    kind: 'hasMany',
    type: 'menu',
    options: {
      async: true,
      inverse: 'action',
      as: 'action'
    }
  }
}

as here is what allows any type to act as the abstract type. Note, the entire field configuration must identically match across all types that satisfy this polymorphic trait.