Bruno Windels 224d56698a only set new live key when creating a fragment after the txn succeeds ... when doing a limited sync, and a new fragment is created, this._lastLiveKey is updated immediately. If the transaction would then fail, the fragmentId in this._lastLiveKey was incremented but the fragment wasn't written to the store, so if sync is resumed and would subsequently succeed, fragmentIds would be assigned to events that don't have a corresponding fragment in the timelineFragment store. This would throw errors when trying to load the timeline, breaking the whole app. This changes SyncWriter to only update this._lastLiveKey in the emit phase, when the transactions has been committed already.		2020-01-04 20:06:49 +01:00
..
domain	add proper import/export functionality	2019-12-14 18:29:35 +01:00
matrix	only set new live key when creating a fragment after the txn succeeds	2020-01-04 20:06:49 +01:00
observable	fix test + bug in ConcatList update	2019-07-29 20:03:22 +02:00
ui/web	add proper import/export functionality	2019-12-14 18:29:35 +01:00
utils	move sortedIndex out of observable as other code will want to use it too	2019-03-08 20:04:28 +01:00
EventEmitter.js	convert tabs to spaces where needed	2019-06-26 22:31:36 +02:00
main.js	add (commented out) instructions how to use record/replay	2019-12-23 14:29:19 +01:00
Platform.js	more WIP	2019-07-26 22:03:57 +02:00
service-worker.template.js	add offline availability with service worker and appcache	2019-09-15 14:32:12 +02:00