Kevin L'Hereec
fa74791c92
The catalog price shown next to a part (e.g. '€979.95') stayed stuck at its initial search-result value even after 'Compare prices' found and persisted a cheaper offer server-side (updatePriceIfCheaper already saves it to the database, but the locally held search result was never updated) — so the UI showed a stale, higher price right above a correctly-labeled 'cheapest' offer, which was confusing (e.g. '€979.95' next to 'Cdiscount: €741.51 (cheapest)'). comparePrices() now also updates part.price locally when the cheapest offer found beats it (or no catalog price was known), mirroring what the backend already persisted, so the display is consistent without needing to re-run the search.