Closed designbystephen closed 2 years ago
I noticed this too yeah, just started running this yesterday 😁 how often is the docker image updated? I'm running that.
Same with Amazon UK
Same with Amazon DE
We need to be able to have the option to NOT do alerts, if it's NOT Sold & Shipped by Amazon. Problem would be solved. 3rd party listings are the problem, when they list them as Used, it will bypass the filters.
Then we should have an OR case instead of a single value element. That way it is more future proof, region independent and etc.
IMO should not be written to match a case by case basis, and instead have the getPrice check for a known set of html elements that can contain the price, eventually returning null (or whatever escapes to logic).
I can take a look at the code later and have better details and maybe a solution.
Then we should have an OR case instead of a single value element. That way it is more future proof, region independent and etc.
IMO should not be written to match a case by case basis, and instead have the getPrice check for a known set of html elements that can contain the price, eventually returning null (or whatever escapes to logic).
I can take a look at the code later and have better details and maybe a solution.
That would probably work for regular items. However, we're talking about graphics cards. I don't think there are many, if any, 3rd parties that are MSRP. I'd rather do away with them all. They also have multi-tabbed product pages. Goodluck.
Same with Amazon DE
Same with Amazon UK
Seems like these need updating too. Maybe we can make a couple issues with these so we can track them?
vale lo stesso per amazon-it
Expected Behavior
Product should be ignored if above max value filter.
info :: ✖ [amazon] [msi (3090)] gaming x trio :: IN STOCK, PRICE xxxx EXCEEDS LIMIT xxxx
The productCurrent Behavior
Currently, the app is logging to the console as "in stock", notifications are being triggered, the web browser is opening, and the product is attempting to add to a cart.
What operating system are you seeing the problem on?
Windows
Relevant log output
Configuration
Code of Conduct