Changes between Version 2 and Version 3 of Ticket #15858, comment 9


Ignore:
Timestamp:
Aug 25, 2012, 10:47:09 AM (7 years ago)
Author:
Peter Jekel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15858, comment 9

    v2 v3  
    11Bill,
    22
    3 The code you listed (introduced in 1.8) is, in my opinion, just a band-aid, to fix only the most obvious case and that is an immediate child was removed. It is a work-around for the underlying problem and does handle any grand children that may have been removed (issue 2). This is also why it doesn't matter if the code snippet listed is deferred or not, you could wait for an hour but you still get the same error.
     3The code you listed (introduced in 1.8) is, in my opinion, just a band-aid, to fix only the most obvious case and that is an immediate child was removed. It is a work-around for the underlying problem and does not handle any grand children that may have been removed (issue 2). This is also why it doesn't matter if the code snippet listed is deferred or not, you could wait for an hour but you still get the same error.
    44
    55Both issues find their origin in the order in which the ItemFileWrite store fires events and how the model handles them. Whenever an item is deleted from the store the store fires an onSet() event for the parent items "children" property BEFORE the onDelete() event is fired. From the store perspective this is perfectly fine as it is independent of any model.