Loading Standards

Expected Behavior

Have consistent rules for where errors are catched and how they are handled during the load process.

Current Behavior

Often safe_load is applied in arbitrary places in the code wherever the developer deemed appropriate.

Possible Solution

• Never raise an exception that bubbles up past load: always finish the load and load "something"
• Use safe_load universally in load_conf.py and nowhere else
• Have submodules raise errors when something bad happens
• Log specific "expected fails" inside of submodules without raising
• Log special errors that need more clarifications inside of submodules
• Only show tracebacks in user code

Context

#126

Start by reading load_conf.py and the submodules involved in the load process, then review the related context in issue #126. Map where safe_load, exceptions, and traceback logging currently occur. Done means the loading and error-handling rules are consistently applied as listed in the proposed solution.