mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Maurice
76b1e67be8
On the desktop, the Immich (or Synology) card could show "Connected" for a server that was down. The settings page loads two answers at once: the saved settings, whose connected flag for Immich only says that a URL and an API key are stored, and the status route, which actually reaches the server. Whichever landed last set the badge. usePhotoProviderConnections had a statusRouteOwnsBadge option that only the phone turned on. The option is gone: whenever a provider declares a status route, only that route sets the badge, on both views. A provider without a status route still takes the badge from its settings read. Regression test FE-COMP-PHOTOPROVIDERS-028 (PhotoProvidersSection.test.tsx) was red on the old code: "Unable to find an element with the text: Not connected" (the late settings read had turned the badge to Connected). Changed assertions: - usePhotoProviderConnections.test.ts FE-COMP-PHOTOCONN-005: it expected the later settings read (connected: false) to override the status route's connected: true; it now checks that a provider without a status route takes the badge from the settings read. - usePhotoProviderConnections.test.ts: render() no longer takes the option, so every call drops its true or false argument.