Juan Tejada d53e0c4a7f [client-app] Correctly show auth error when we can't connect to n1cloud ... Summary: Previously, n1 cloud auth errors were stuffed into an account's syncState. The problem with that is that the sync loop manages that state, and as long as the sync loop is running it will set that state to running. However, it might be the case that the sync loop is running but we can't connect to n1Cloud, so even though we would set the `syncState` to `n1_cloud_auth_failed`, the sync loop would just set it back to 'running', and the user wouldn't see the error notification indicating that it can't connect to n1Cloud This commit makes it so we keep tracj of the auth failure state for n1Cloud in a separate field, and makes sure that the error notification component shows that error. Test Plan: manual Reviewers: mark, spang, evan, halla Reviewed By: evan, halla Differential Revision: https://phab.nylas.com/D4172		2017-03-10 15:56:41 -08:00
..
assets
lib	[client-app] Correctly show auth error when we can't connect to n1cloud	2017-03-10 15:56:41 -08:00
spec	[client-app] Report source when reporting open times for accts window	2017-02-23 16:17:50 -08:00
stylesheets
package.json