CrudManager responding to failed remove requests should restore records from removed Bag

[ExtAnimal]

Forum post

If the server responds to a sync request that contains

events : {
    removed : [{ id : 1 }, { id : 2}]
}

with a response that contains

events : {
    removed : [{ id : 1}]
}

The it should restore record id 2 from the Store's removed Bag.

The code in CrudManager does strange things. AbstractCrudManager.getRowsToApplyChangesTo collects respondedIds and if the responded ids do not contain all the ids that weer passed to the server in the remove block, it adds them back in.

So the server can never respond with a reply that tells the CrudManager it didn't manage to delete the records. If the server sends rows : [{ id <deleted record Id> }], the record will be considered an added record.

As it stands, I cannot see the store's removed Bag being processed at all. The removed records stay in there after the sync response.

This area needs some thorough testing using t.mockAjax.

[ExtAnimal]

Failing test case added in this branch: https://github.com/bryntum/bryntum-suite/pull/6197