View Full Version : [FIXED] "dropped"-state of model is not reset on model.reject()

19 Sep 2014, 4:18 AM
If I call "drop()" on a clean model in my store, the model is removed from the store. Then I call "rejectChanges()" on the store and the model gets restored. However, if I try to drop the same model again nothing happens. This is because the model still has its "dropped"-state set to true which in turn causes the drop() method to immediately return without doing anything.

Is there something I am missing?


23 Sep 2014, 9:38 AM
I added the runnable test case and am opening a bug for this.

6 Dec 2014, 2:23 AM
The override is here -> http://www.sencha.com/forum/showthread.php?295614
(http://www.sencha.com/forum/showthread.php?2956142.5)2.5 months later the single line is not integrated and the release-notes doesn't mention this bug, and no clear full list of known bugs are provided anywhere. That costed us more than $1500 in wasted time to track down. No respect here, it's clear that Sencha is not trying to setup the environment to make it efficient to develop with their product.

12 Dec 2014, 4:47 AM
If you care about this specific bug you are likely be also hit by the following -> http://www.sencha.com/forum/showthread.php?295799-the-store-getRemovedRecords-no-empty-after-saving-to-server-via-session.getSaveBatch

I (http://www.sencha.com/forum/showthread.php?295799-the-store-getRemovedRecords-no-empty-after-saving-to-server-via-session.getSaveBatchI) think delete use cases have never been coded or tested before 2 weeks ago.