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
{{ message }}
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.
Scraper called with errors array as an argument that can be pushed to (feels weird man)
Scraper called with this = { errors: [] } (breaks a lot of scrapers)
Scraper called with region array as an argument you can push data to, can throw at any time (i.e. throw at the end of the scraper to indicate a non-fatal error)
Other ways?
The text was updated successfully, but these errors were encountered:
To me, idea 1 errors array isn't bad, it's a collector parameter. Have used such things in the past. Could even be a stream or a logger they push to.
Other possibility: global logging, potentially. Scrapers could instantiate a ScraperError(this, err) and give it to a global logger routine. If scrapers know they can continue despite the error, great.
A couple ways this could work:
errors
array as an argument that can be pushed to (feels weird man)this = { errors: [] }
(breaks a lot of scrapers)region
array as an argument you can push data to, can throw at any time (i.e. throw at the end of the scraper to indicate a non-fatal error)The text was updated successfully, but these errors were encountered: