You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3b5521c
Browse filesBrowse the repository at this point in the historyBrowse files
committed
fix(mobile): keep the search spinner for the whole directory refresh
The scoped directory status does not cover a production refresh end to
end. It turns loading only after memberships and metadata arrive, and
loaded before display names, latest messages and the new list are
installed. With fast message and people replies, the spinner stopped
and "No results" showed while the refresh was still running.
Search again tracks the directory load it started until its future
completes. A token, which rebuild drops, fences it, so a load from an
earlier community cannot settle a newer one. A failure notice stays
hidden while the next load runs.
The journey fake now follows production order and checks scope. A new
test drives the real ensureDirectoryLoaded -> retryDirectory path with
the membership query held at the relay boundary.
Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Logan Johnson <[email protected]>
// Another caller's directory load keeps the spinner on until it ends,
301
+
// though this search's own request returns at once.
302
+
final container =ProviderScope.containerOf(
303
+
tester.element(find.byType(SearchPage)),
304
+
);
305
+
final status = container.read(channelDirectoryLoadStatusProvider.notifier);
306
+
final scope =channelDirectoryScope('http://community.test', 'test');
0 commit comments