[feature] Ability to use the advanced filter techniques for "price watch" mode

[kquinsland]

Version and OS

0.49.17, Linux/k8s

Is your feature request related to a problem? Please describe.

One of the pages that I am scraping for price information is littered with other "previews" of related products/skus. This trips up the scrape/code in "price watch" mode with an error like this:

Cannot run, more than one price detected, this plugin is only for product pages with ONE product, try the content-change detection mode.

Describe the solution you'd like

For this particular page, the primary SKU/price/availability data that I am concerned with is reliably available via a particular XPATH selector. I was wondering why it is not possible to use all the advanced selector/filter settings from the "change detection" mode as one step in a "chain" and only after cutting out the 'noise', use the price/availability detection mode.

Describe the use-case and give concrete real-world examples

Here is an example URL: https://www.homedepot.com/p/Samsung-Bespoke-5-3-cu-ft-Ultra-Capacity-All-In-One-Washer-Dryer-Combo-with-Super-Speed-and-Ventless-Heat-Pump-in-Dark-Steel-WD53DBA900HZ/328419334

Below the main content there are a few carousels ("customers also viewed", "more from $vendor" ... etc) which feature mini "previews" complete with prices. I am confident that this is where the price detection logic is getting caught up.

If I could say "monitor for $price, but only in the <div> that $thisXPath points to..." that would be fantastic.

Additional context
Add any other context or screenshots about the feature request here.

[dgtlmoon]

the price/restock "mode" reads the pages LD-JSON embedded data, not the other content, the xpath filters wont help so much here

EXCEPT for the case where the page has no LD-JSON or similar, then it will try to find atleast the right keywords to know if its in stock or not

[kquinsland]

pages LD-JSON embedded data, not the other content,

Huh. TIL about LD-JSON! Funny enough, one of the pages that I am using for testing has multiple type="application/ld+json" script blocks in the html; the block with the largest payload actually has data for every variant/sku of the item which is helpful for my purposes but should also trip the "multiple prices detected" case ... but does not.

Another one of my test cases does not appear to use json-ld which is where I am getting the "multiple prices detected" error and that is the case where xpath filtering would be helpful.

So if I'm understanding you correctly, the price/re-stock mode is the more precise mode but unlikely to work unless the scrape target has been designed for this case; I should be using the regular "text/diff" mode for most things?

[dgtlmoon]

So i think you want this one #2946

I'll close this issue off

So if I'm understanding you correctly, the price/re-stock mode is the more precise mode but unlikely to work unless the scrape target has been designed for this case; I should be using the regular "text/diff" mode for most things?

correct, if the page has no LD+JSON ( or similar data) , then it will atleast try to scrape the keywords to see if its in stock or not (but not price, yet)

[dgtlmoon]

fixed in #3506