Establish some consistent convention on what/where to throw and catch exceptions.

opengamedata / opengamedata-core

Python framework for extracting features from OpenGameData event datasets.

https://opengamedata.fielddaylab.wisc.edu/

MIT License

1 stars 3 forks source link

Establish some consistent convention on what/where to throw and catch exceptions. #127

Open LswaN58 opened 3 months ago

LswaN58 commented 3 months ago

In particular, it would be nice to say "Extractors always throw exceptions instead of logging warnings/errors." But more thought would be needed on how those should get handled upstream, and would need to double-check that the "fail fast" setting is still working.