Closed SorenZ closed 6 years ago
I need to have public setter access to Id property.
why?
In my case IEntity
have Id
property with public getter and setter (its standard in my framework)
Maybe I was wrong and should change IEntity
.
The changes here should be just around MongoUserStore
and some tests for that.
@tugberkugurlu
I've changed back MongoUserStore
, and try to solve my problem with parameterized constructors.
Could you also add some tests around this?
@tugberkugurlu Of course. I watched carefully you build test projects and infra for in place testing. I love to complete testing project, I had busy days but I will work on testing in near future. just like main AspNet/Identity test project.
@SorenZ 👋 any updates on the tests for this to highlight what works and what does not?
@SorenZ 👋 any updates on the tests for this to highlight what works and what does not?
Hi @SorenZ 👋 I will close this for now as we are try to get this back up and this PR is a bit behind. Feel free to reopen, add tests and we can think about getting this working again 👍 /cc @dealproc
NotSupportedException: Store does not implement IQueryableUserStore<TUser>
In case when we want to query on users through Store (UserManager
) and get information about usersauto-property accessor has conflict with
MongoIdentityUser
expansions by inheritance to new Model in my scenario I have a model that inherit fromMongoIdentityUser
I need to have public setter access to Id property. I didn't want to create a PR for two different subject but GitHub merge it.