Currently, the configuration is passed in via a big yaml file that gets parsed into a dictionary. This is a bit inconvienient as it neither documents what configuration values are available and it pollutes the main function. Maybe it would be nice to refactor it out into a separate class?
Currently, the configuration is passed in via a big yaml file that gets parsed into a dictionary. This is a bit inconvienient as it neither documents what configuration values are available and it pollutes the main function. Maybe it would be nice to refactor it out into a separate class?