Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't think this is 'done', but it is easier to work with. In particular I don't think I've got the control with the 'pretty' flag quite right. However I'm hopeful it can be iterated from here.
I think we can use Rich 'everywhere' if I've understood the documentation correctly. I think a way to manage this is to just output 'logging' from the Scrapers, and have nice cli reporting handled in the Commands. This way when the
scraper_worker_handler
runs the scraper directly (rather than through the Command) we get the logging with out the boxes/columns/progress bars.I've merged this into #13 in order to see how it plays with the handlers and the whole sam deploy.