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
Considering that the SaveChangesAsync function actually returns something, why does the Update and Delete operation not return that value?
This is not really a show stopper for me since I can always override that class and copy the same implementation, but I'm just curious if there's any reason why this is made this way?
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. Yes, we might return something. No one complained until now, so it has remained that way.
But, the question would be what to return. Should we return entities back for Update or the affected rows?
Let's keep this issue open for a while and wait for feedback from the community. Once we have a consensus on what to return, then sure we'll change it.
Looking at here,
RepositoryBaseOfT
class:Considering that the
SaveChangesAsync
function actually returns something, why does the Update and Delete operation not return that value?This is not really a show stopper for me since I can always override that class and copy the same implementation, but I'm just curious if there's any reason why this is made this way?
The text was updated successfully, but these errors were encountered: