Replies: 1 comment 2 replies
-
To simplify the CSS selectors or XPath expressions, you can use group targeting to select the desired cells in fewer filters. Here's how you can achieve it: Then you can have just 2 rows in your notification XPath
CSS Selector
These filters use positional constraints to target only the first three cells in each specified row. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm quite new to pretty much all the ecosystem of changedetection.io (jinja, xpath ecc)
I've currently set up a monitor to a webpage which is supposed to send me notification over telegram.
Every works great except that it takes me 1 minute to exactly decipher what has changed and i suspect this has something to do with my profeciency and understanding of the tool
My filters are set up as follow
/html/body/main/section/div/table/tbody/tr[60]/td[1]
/html/body/main/section/div/table/tbody/tr[60]/td[2]
/html/body/main/section/div/table/tbody/tr[60]/td[3]
/html/body/main/section/div/table/tbody/tr[61]/td[1]
/html/body/main/section/div/table/tbody/tr[61]/td[2]
/html/body/main/section/div/table/tbody/tr[61]/td[3]
......
as you can see it is a table with three columns and many rows (here 2 in the example).
The notification is set to default {{diff}} and i was hoping to only highlight the diff but it's showing all the content extracted from the filter without respecting any table format or newline (im at fault here i guess because i dont know how to make it better) but i would prefer to only see the line that actualy changed and maybe with the format
I haven't tested {{diff_removed}} or {{diff_added}} too see if they would help (page changes rarely and i just recently did this change).
But what if i want a notification like
(Assume it is tr[60] that triggered the notification)
Before:
/tr[60]/td[1] - /tr[60]/td[2] - /tr[60]/td[3]
After:
/tr[60]/td[1] - /tr[60]/td[2] - /tr[60]/td[3]
without any "garbage" data such as all the other tr[x]
Is there a way to do so without having to create many individual monitor?
Beta Was this translation helpful? Give feedback.
All reactions