I read the description of this issue and specially the things to be decided:
Location: we could put this on either ChangeTracker or on DbContext directly.
Naming: Pick one between HasChanges, IsDirty and changing the signature of DetectChanges to return a result.
Return value: bool or int containing number of pending changes (analogous to SaveChanges result).
I'm interested to create a new contribution for this issue, some things I'm thinking:
Unai
Location: we could put this on either ChangeTracker or on DbContext directly.
Naming: Pick one between HasChanges, IsDirty and changing the signature of DetectChanges to return a result.
Return value: bool or int containing number of pending changes (analogous to SaveChanges result).
I'm interested to create a new contribution for this issue, some things I'm thinking:
-
Location: ChangeTracker, is more natural because the DetectChanges is alredy here.
-
Name: HasChanges
-
Return value: return the number of changes instead of bool is a good idea
Unai