Description of the Issue:
As @rjoussen rightly pointed out in #331, all of our data processors currently take a file_options_dict argument, which contains additional options for each data processor. These dictionaries are highly unintuitive to use because their expected contents are not known beforehand, and without looking at the code.
Proposed Solution:
Refactor file_options_dict into a data class or similar.
Action Items:
No response
Related Issues:
No response
Interested Parties:
@rjoussen
Description of the Issue:
As @rjoussen rightly pointed out in #331, all of our data processors currently take a
file_options_dictargument, which contains additional options for each data processor. These dictionaries are highly unintuitive to use because their expected contents are not known beforehand, and without looking at the code.Proposed Solution:
Refactor
file_options_dictinto a data class or similar.Action Items:
No response
Related Issues:
No response
Interested Parties:
@rjoussen