0b644aa733
Photos stored on disk are CSS-trap distorted (hue rotation baked in). The frontend uses WasmImage + per-photo restoreKey to reverse the distortion at render time. Before this fix, applyPhotoRewrite rewrote src/webpSrc for API-fetched gallery + shop data but never attached a restoreKey, so every photo rendered with a visible rainbow tint (the trap in its raw form) after the /provider-api/api/data fetch replaced the initial state. - Add ProviderSiteConfig.getPhotoRestoreKey as a second deployment hook alongside rewritePhotoSrc. Quinn deployment wires it to the virtual:photo-css-traps module. - applyPhotoRewrite now takes getRestoreKey and attaches restoreKey to every gallery/shop photo. Lookup uses webpSrc when present since that is what WasmImage actually fetches. - ShopListingPhoto gains an optional restoreKey field. - PageIllustration + DestinationsPage swap ProtectedImage → PhotoImage and pull restoreKey via useProviderConfig().getPhotoRestoreKey so their illustrations restore too. DuosPage and SpecialtiesPage already used PhotoImage + virtual:photo-css-traps directly so they were already fine. |
||
|---|---|---|
| .. | ||
| backend-api | ||
| data-api | ||
| frontend-public | ||
| shared/src | ||