0

I have yet to fully understand the need to implement IEditableObject for an entity. I can only think about it's use when an entity has to revert the changes back to it's previous state, for example a Reset/Revert behavior on a dialog.

Consider the same above scenario where the user has to revert the entity state on a CRUD screen to it's beginning state. Does an entity derived from BreezeSharp BaseEntity support the rollback feature already? Or should the client implement it's own state management, so don't depend on the BreezeSharp for the same?

wonderful world
  • 10,969
  • 20
  • 97
  • 194

1 Answers1

1

The reason that breeze implements IEditableObject is that many UI suites offer substantially greater functionality to objects that implement IEditableObject and all of the requirements of IEditableObject are already part of the breeze Entity implementation anyway, so the actually implementation is simply an exercise in delegation.

If you are using Breeze.sharp, I can't imagine why you would want to implement your own state management since Breeze already implements most of what I think of as state management. What is it that you need that Breeze does not provide in this area?

Jay Traband
  • 17,053
  • 1
  • 23
  • 44
  • What I'm looking for is a rollback functionality with CancelEdit. With this, the whole entity will revert to it's initial state. As an example, the Employee.FirstName has the value of 'John' which has been changed to 'Matt'. With the CancelEdit, the entity will be reverted, so the FirstName will be set to 'John' again. – wonderful world Jul 14 '14 at 18:57
  • @wonderfulworld On the client you can always call thisEntity.entityAspect.rejectChanges() on each entity to revert to it's initial state. The manager has a rejectChanges() method as well that rejects *all* changes inside of the manager which haven't been saved. I believe this is what you are looking for already. – PW Kad Jul 14 '14 at 19:53
  • Yes. That's what I was looking for. – wonderful world Jul 14 '14 at 20:13