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
Just taking a look at this lib as I liked your blurb and I'm looking for a .NET focused method for using IndexedDb. The docs seem to be a little bit out of sync with the latest code and wanted to seek some clarification around the data record classes.
It seems that the current code base as demonstrated in the TestBase project require that data models are required to implement IMagicTable<>, with a slightly ambiguous generic type. Am I understanding this correctly? This approach infringes on the single-responsibility principle and couples the data model to the database implementation. This though doesn't appear to be detailed in the documentation and I was wondering what the plans for this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Just taking a look at this lib as I liked your blurb and I'm looking for a .NET focused method for using IndexedDb. The docs seem to be a little bit out of sync with the latest code and wanted to seek some clarification around the data record classes.
It seems that the current code base as demonstrated in the TestBase project require that data models are required to implement IMagicTable<>, with a slightly ambiguous generic type. Am I understanding this correctly? This approach infringes on the single-responsibility principle and couples the data model to the database implementation. This though doesn't appear to be detailed in the documentation and I was wondering what the plans for this.
Beta Was this translation helpful? Give feedback.
All reactions