mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-02-23 07:36:12 +08:00
Summary: The issue was that when selecting a thread id, it was not loaded in the current list of items in the ThreadList and failing to come up. The notifications now pass a property that the AccountSidebarStore listens for to indicate what tag we think is most likely to contain the thread that we're directly trying to access. Eventually the correct data set may be loaded that contains the thread we want. In the meantime, the requested selectedThreadId may or may not resolve to an actual selectedThread object. If we detect that the requested thread came into scope, we trigger another action to notify everyone that the thread is now available. We also pass along a force flag since this is a case when the requested thread id hasn't changed Test Plan: edgehill --test Reviewers: bengotow Reviewed By: bengotow Differential Revision: https://review.inboxapp.com/D1353 |
||
---|---|---|
.. | ||
main.coffee |