infinite-persistence 38c13cf5ef Skip USER_STATE_POPULATE when sync_hash is the same ... ## Changes - doHandleSyncComplete: only call doGetAndPopulatePreferences when there is new data. - But for that to work, we'll need to populate preferences at least once. We'll do that in doSignIn. - We can also remove the "sync/prefs ready" mechanism that was mainly meant for Desktop. Then came another problem: while trying to spark changes between 2 tabs, `sync/get` was saying "no change" despite the local and server hash being different. I think it is because the both `sync_hash + sync/get` combo is operating on server data, so the hash is the same. I'm guessing this is why we ended up just running doGetAndPopulatePreferences every time before PR, since this flag wasn't correct in this scenario. - Updated `data.changed` to consider both API results and comparison with local hash.		2021-11-15 07:06:39 -08:00
..
index.js	Skip USER_STATE_POPULATE when sync_hash is the same	2021-11-15 07:06:39 -08:00
view.jsx	Skip USER_STATE_POPULATE when sync_hash is the same	2021-11-15 07:06:39 -08:00