RoleStore missing functionality

Apr 2, 2014 at 12:24 AM
I haventh been able to find much info about it.

But lately i have been using Identity, but i come to a problem, best practice is 1 DbContext per request, but also best to make all changes to the DbContext and in the end save the changes. (Batch transaction)

However RoleStore doesnt seem to implement AutoSaveChanges variable as UserStore does, so would have to make my own version just to get around this.
Is this something which is meant to be, or was missed?
Apr 2, 2014 at 5:47 PM
@Zaixu: The UserStore works on the user object which has other dependent objects like Logins, claims and roles and hence the state is unpredictable. The auto save is added since for a particular CRUD operation we might not know the state of the user object and the user may choose to do a batch update at end of multiple changes on the user object. The RoleStore works contains basic CRUD operations only on the Role class whose state is predictable due to no dependent objects. Hence update is done with each operation. You can file a bug and we can triage this for next release if you think the team should reconsider this.