You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Single Table Design is the new hotness, at present the stores are limited to one type. I propose a Multi Model
Store, where a key default type key is used for looking up the mappings to apply to that item. This type key (lookup) can be configured as a global config or at the multimodel level for robustness.
The Db Item is not instantiated via its class (which I feel is a good thing) but mappings are applied.
the type key is configurable as a global or at a 'store level`
Describe the solution you'd like
I am happy to tackle this is pointed in the right directions
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Single Table Design is the new hotness, at present the stores are limited to one type. I propose a Multi Model
Store, where a key default
type
key is used for looking up the mappings to apply to that item. Thistype
key (lookup) can be configured as a global config or at the multimodel level for robustness.The Db Item is not
instantiated
via its class (which I feel is a good thing) but mappings are applied.the
type
key is configurable as a global or at a 'store level`Describe the solution you'd like
I am happy to tackle this is pointed in the right directions
The text was updated successfully, but these errors were encountered: