Open raphodn opened 6 months ago
I think it conflicts a little with this idea I've had with adding prices from flyers/leaflets and maybe with GDPR requests
https://openfoodfacts.slack.com/archives/C02Q6KM7F/p1707152495571579
Maybe it makes sense to do that checking depending on proof type - e.g. PRICE_TAG
or RECEIPT
should be connected to a location but GDPR_REQUEST
or FLYER
(if we decide to add it in the future) not necessarily.
What do you think?
Story
On price add, we need to check that a same proof is used with the same location as other existing prices for this proof