Juan Tejada 575ff4a73e [local-sync] Ensure messages always have a uid after syncback tasks ... Summary: Syncback tasks that move messages to a different folder used to leave those messages without a uid because it was unknown at the moment, and it would only be discovered later on in the sync loop. This had the unwanted effect of not allowing you to perform more than 1 syncback action on the same thread back to back (e.g. undoing an archive, or sending and archiving immediately) This commit makes it so that `SetThreadFolderAndLabels` and `MoveThreadToFolder` runs a new sync task to fetch the new uids for the moved messages. We do this via a new sync task, `FetchNewMessagesInFolder` which /only/ fetches new messages in a folder (no fetching old messages or attribute updates). This is a first step to cleaning up the gigantic `FetchMessagesInFolder` task into smaller parts-- but that will come in a separate diff. For now we want to fix the immediate problem. See D3788 and D3789 for more details Test Plan: manually move threads around, undo moving threads, reply on a thread and immediately archive Reviewers: khamidou, mark, spang, halla, evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D3798		2017-01-27 08:28:33 -08:00
..
images	[dashboard] Put dashboard into work window	2016-11-28 18:02:42 -08:00
spec	Fix unit test path.	2017-01-15 14:09:05 -08:00
src	[local-sync] Ensure messages always have a uid after syncback tasks	2017-01-27 08:28:33 -08:00
stylesheets	[💄] fix eslint issues before they get overwhelming	2016-12-01 15:37:48 -08:00
main.es6	[local-sync] Cleanup sync tasks to be more consistent with syncback tasks	2017-01-13 12:30:43 -08:00
package.json	Update Nylas N1 to Nylas Mail	2017-01-12 11:25:39 -08:00