abaevbog 07066fd8c1 Fix relations to erased items reappearing after sync (#5486) ... Fix ghost relations to erased items reappearing after sync. The dataserver ensures that related relations are bidirectional. If a related item is erased, syncing would first upload the update to the remaining related item (where the relation is removed), followed by the deletions. While handling update upload, the dataserver would return the old, should-be-removed, "dc:relation" entry for that item because it does not know that the other item is erased. To handle this, swap the order of operations during sync: upload deletion first and then upload updates after. Then, when the dataserver handles the update of the non-erased item, there is no related item to enforce bidirectional relations to. Fixes: #5481		2025-08-15 02:00:43 -04:00
..
components	fx140: Asyncify/ESMify tests	2025-07-30 22:30:53 -04:00
content	Don't merge into a missing snapshot attachment (#5459)	2025-08-02 01:53:47 -04:00
resource	Remove Chai as Promised	2025-07-30 22:31:08 -04:00
tests	Fix relations to erased items reappearing after sync (#5486)	2025-08-15 02:00:43 -04:00
chrome.manifest	fx115: Restore test runner	2024-03-30 00:58:53 -04:00
runtests.sh	fx140: Use architecture-specific build folder for tests on Linux (#5445)	2025-07-31 22:48:21 -04:00