dgtlmoon / dgtlmoon/changedetection.io
Ability to perfrom additional steps after data has been captured
- Dominant language
- Python
- Stars
- 34.1k
- Forks
- 2k
- Avg merge
- 22h 52m
- Merged PRs (30d)
- 70
Description
Version and OS
v0.40.3 running in docker/linux
I have been using the browser steps feature to accomplish the things below.
I have some sites that once you login in, you can not log in again from a different session until you log out the current session.
I use this site to capture two different areas of interest but if my first watch has run my second watch will fail as is will not be able to log in again. Performing step after login will all fail as the site wont let me go past login. The only option left is wait for a 20+ minutes for the site automatically kill the session.
What would be useful is to have additional steps after the data is captured. e.g When all steps preformed and data is captured and notification is send then click the sign out button on the page.
This would enable my second or third watch for that site to always have successful logins.
Contributor guide
Research direction
Start by tracing the browser-steps flow through data capture and notification in the repository; the payload does not name specific files or tests. Done means an additional step, such as clicking a sign-out button, can run after capture and notification so later watches can log in successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100