mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-01-08 17:17:56 +08:00
ff5c88ed69
Summary: fixes T3563 todo [x] check with @bengotow and @evan -- does this solution make sense to you? [x] decide on the actual visual cue to the user -- @bengotow you suggested a loader or spinner, but i was thinking that actual copy should be used so it doesn't look like an unhelpful spinner which goes indefinitely. what do you think of the copy here? [ ] implement spinner similar to sending a draft [ ] write tests [ ] verify that we're showing progress in a helpful way problem - new users would see nothing in edgehill after they log in, with no indication on why they can't see any of their mail - in actuality, our backend is actively pulling all their mail to serve it to edgehill - new users think edgehill is broken because they're unaware of the work that our backend was doing solution - when the backend sends deltas to edgehill, we show a message in the activity bar saying that we're trying to get their mail - we'll show the sync progress Test Plan: still need to add tests. all previous tests still green. Reviewers: bengotow, evan Subscribers: sdw, bengotow, evan Maniphest Tasks: T3563 Differential Revision: https://phab.nylas.com/D2032 |
||
---|---|---|
.. | ||
main.coffee | ||
nylas-long-connection.coffee | ||
nylas-sync-worker-pool.coffee | ||
nylas-sync-worker.coffee |