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
{{ message }}
This repository has been archived by the owner on Aug 27, 2019. It is now read-only.
This is more of a question than an issue however it may be worth looking into in general.
Has there be any thought to allowing an end user to inherit from and extend your core models (Client, Scope, etc...) and then inject the extended modules, probably through a factory, possibly a method on EntityFrameworkServiceFactory or even and overloaded constructor?
In my situation I am persisting my data to SQL Server, through EF and using Identity 2.0. Everything is working great but I am creating a lot of join tables (i.e. to link a specific client to a specific user) as part of a larger security model. These join tables are a simply as id, clientid, userid and while they get the job done, it would be nice to be able to extend them in a similar fashion to how IdentityUser can be extended. This would also allow for the creation of new navigation properties. Now of course this would require overridden stores and managers but I think it may be a valuable add.
Thank you for all of the great work that you and Dominick do.
Regards,
James Legan
The text was updated successfully, but these errors were encountered:
Brock,
This is more of a question than an issue however it may be worth looking into in general.
Has there be any thought to allowing an end user to inherit from and extend your core models (Client, Scope, etc...) and then inject the extended modules, probably through a factory, possibly a method on EntityFrameworkServiceFactory or even and overloaded constructor?
In my situation I am persisting my data to SQL Server, through EF and using Identity 2.0. Everything is working great but I am creating a lot of join tables (i.e. to link a specific client to a specific user) as part of a larger security model. These join tables are a simply as id, clientid, userid and while they get the job done, it would be nice to be able to extend them in a similar fashion to how IdentityUser can be extended. This would also allow for the creation of new navigation properties. Now of course this would require overridden stores and managers but I think it may be a valuable add.
Thank you for all of the great work that you and Dominick do.
Regards,
James Legan
The text was updated successfully, but these errors were encountered: