Two-stage mount splits the propagation map's first paint: the static HTTP render still fetches scores synchronously so SEO/noscript shipping gets real data baked into `data-scores`, but the websocket-connected mount defers the potentially-slow fetch to `start_async/3`. Chrome paints immediately; scores stream in via an `update_scores` push_event once `handle_async(:initial_scores, ...)` resolves. A small overlay (spinner on `:loading`, retry button on `:failed`) uses `<.async_result>` so users can see state and recover from a transient fetch error. |
||
|---|---|---|
| .. | ||
| admin | ||
| beacon_live | ||
| contact_live | ||
| user_management_live | ||
| about_live.ex | ||
| algo_live.ex | ||
| contact_map_live.ex | ||
| import_live.ex | ||
| map_live.ex | ||
| path_live.ex | ||
| privacy_live.ex | ||
| rover_live.ex | ||
| status_live.ex | ||
| submit_live.ex | ||
| user_profile_live.ex | ||
| weather_map_live.ex | ||