You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came to me after thinking more about #28 and realizing that this could be a better way to add this and similar features without creating bloat.
It would be helpful if russ had the option to run a post-processing script after items are loaded from a feed. Ideally the script would be passed a list of database IDs (as a list of arguments) for the new feed items so it can do whatever needs to be done for those items, in whatever order is best.
Some potential use cases:
Fetching HTML article contents and parsing them into text
Fetching article images and storing them somewhere
Running filters to remove articles that match or don't match certain keywords/tags
It would be better to set this script at the individual feed level, as this would allow users to easily set different post-processors for different feeds.
I'm not sure whether or not russ should wait for the script to complete, and how long it should wait. For simplicity's sake it may be best to just wait with a spinner or something to indicate activity, with the user able to press some key to stop waiting. If and when the script finishes, the user would see success or failure status.
The text was updated successfully, but these errors were encountered:
This is a very interesting idea but I'm not interested in adding a scripting interface to russ at this time. I do want to thank you both for opening the issue and for typing up an exploration of this idea. Scripting may be something I revisit in the future.
Is there an existing issue for this?
Feature description
This came to me after thinking more about #28 and realizing that this could be a better way to add this and similar features without creating bloat.
It would be helpful if russ had the option to run a post-processing script after items are loaded from a feed. Ideally the script would be passed a list of database IDs (as a list of arguments) for the new feed items so it can do whatever needs to be done for those items, in whatever order is best.
Some potential use cases:
It would be better to set this script at the individual feed level, as this would allow users to easily set different post-processors for different feeds.
I'm not sure whether or not russ should wait for the script to complete, and how long it should wait. For simplicity's sake it may be best to just wait with a spinner or something to indicate activity, with the user able to press some key to stop waiting. If and when the script finishes, the user would see success or failure status.
The text was updated successfully, but these errors were encountered: