Repository navigation
Explain slow FW Lite project opens with a toast - #2822
Conversation
The first open after an update can rebuild a project's snapshots, which
takes minutes on large projects while the skeletons look stuck. After 1.5s
a toast the user can't close says the project is opening; after 8s it
explains the wait and asks the user to keep the app open; a slow open ends
with "{name} is ready".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AM78WCP3niyYAq8xbED82r
|
No actionable comments were generated in the recent review.
|
|
[Claude, autonomous]
Generated by Claude Code |
|
@hahn-kev what do you think? I like how generic it is (i.e. no specific events or checks) and how it hopefully makes long waits just chatty enough to assure users that nothing is wrong, there is probably a legitimate reason for the wait and their waiting is not in vain 😅 |
Start the toast before the name lookup, and just dismiss it when the open returns: "ready" could show while the page is still loading its own data. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
[Claude, autonomous]
Shows a loading toast while a CRDT project opens, so the full snapshot rebuild from #2813 doesn't look stuck.
Screenshots (FwLiteWeb, with an artificial 10s delay before the open). These show an earlier version that included the project name and a "ready" state; the toast's position and style are unchanged:
🤖 Generated with Claude Code
https://claude.ai/code/session_01AM78WCP3niyYAq8xbED82r