Changes between Initial Version and Version 2 of Ticket #17642


Ignore:
Timestamp:
Jan 9, 2014, 4:33:32 PM (7 years ago)
Author:
Sebastien Brunot
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17642

    • Property Owner set to Kris Zyp
    • Property Status changed from new to assigned
    • Property Component changed from General to Data
    • Property Summary changed from Observable does not properly report the position of objects added using the before option to Observable cannot properly report the position of objects added using the before option

  • Ticket #17642 – Description

    initial v2  
    1 When a Store is wrapped into an Observable, and its add method is called with a non null before parameter in the options (for a store that supports ordering of its elements), the new position of the added element is wrongly reported to the observer.
    2 
    3 This can be simply verified using a MemoryStore.
     1When a Store is wrapped into an Observable, and its add method is called with a non null before parameter in the options (for a store that supports ordering of its elements), the new position of the added element cannot be reported to the observer.
    42
    53It seems that the issue is a design issue: when calling add, the observable rely on the queryExecutor to order the added element in the query result. The problem is that the queryExecutor has no information about the options provided to the add method, and thus cannot use the value of the before parameter to calculate its result.