This disparity is annoying and makes logging less reliable:
2024-02-24 17:14:17 | INFO | Collected 1095 total bookmarks.
2024-02-24 17:14:17 | INFO | Includes 18 favourites.
2024-02-24 17:14:17 | INFO | db holds 19 favourited rds previously tracked
2024-02-24 17:14:17 | INFO | Total untracked favourites found: 0
It will be nice SQLite practice.
There may be a simple path - create additional fields in the db:
{
'removed': 'True',
'removal_date': '<date>'
}
Then update the logging logic (and perhaps logic in other places) to exclude 'removed' rds.
This could be worth considering alongside #17 as both are adding fields to the db.
Relies on #13.
Why!? Yes, it's not strictly but...
This disparity is annoying and makes logging less reliable:
It will be nice SQLite practice.
There may be a simple path - create additional fields in the db:
Then update the logging logic (and perhaps logic in other places) to exclude
'removed'rds.This could be worth considering alongside #17 as both are adding fields to the db.