Open prakhar1989 opened 8 years ago
Interesting usecase! I think we should keep track of all 3. This might be difficult to do, but as a user, I want to keep track of all the prices for a particular product.
Ah.. sounds like a good plan. It might not be terribly hard to scrape this info from the extension / crawler, but we'll need to think about how to notify the user. If the price of each type of book, goes down by $1, we should generate just one notification rather than three - which might get a bit complicated.
Itn't there a way to have a nested pricing strucutre? Like one notification for all the prices associated with a product. We might have to think about the model of the db now?
You can but you'll need to maintain that association in the backend. And it'll get really complex very quickly. Even the scheduling logic will be written in such a way to handle this complexity. The other option is that we batch all notifications to a user when we send an email. On Nov 20, 2015 1:29 AM, "Vinay Gaba" notifications@github.com wrote:
Itn't there a way to have a nested pricing strucutre? Like one notification for all the prices associated with a product. We might have to think about the model of the db now?
— Reply to this email directly or view it on GitHub https://github.com/prakhar1989/pricetell/issues/7#issuecomment-158294545 .
Guys,
We need to take a call on how do we handle product pages where multiple prices are applicable. For example, a product page for a book on Amazon has a Kindle edition, a Paperback edition and a Hardcover edition. Same for movies on Amazon. Any ideas on how to handle these cases - considering that we need to handle the same scenario while scraping the website?