useNetworkConfig always performs a fresh fetch on mount. On the landing page you now render both NetworkSwitcher (in the header) and NetworkBadge, so this will trigger duplicate /api/config requests on initial load. Consider introducing a shared cache (module-level promise/result, a context/provider, or a data-fetching library) so multiple consumers reuse the same request/result.
Originally posted by @Copilot in #472 (comment)
we should make sure we aren't unnecessarily pinging /api/config.. confirm backend has cached response (it should be the same per startup) or that we optimize calls on the front-end. no need to make unnecessary network calls if we can help it easily
useNetworkConfigalways performs a fresh fetch on mount. On the landing page you now render bothNetworkSwitcher(in the header) andNetworkBadge, so this will trigger duplicate/api/configrequests on initial load. Consider introducing a shared cache (module-level promise/result, a context/provider, or a data-fetching library) so multiple consumers reuse the same request/result.Originally posted by @Copilot in #472 (comment)
we should make sure we aren't unnecessarily pinging /api/config.. confirm backend has cached response (it should be the same per startup) or that we optimize calls on the front-end. no need to make unnecessary network calls if we can help it easily