Closed nflorin closed 3 years ago
I think there are several things that need to happen:
configparser
text file to something nested like YAML, so we can associate issues with specific files[DEFAULT]
issue set that the regular interactive validator deals with, to the exclusion of the other issue sets (which won't normally be in the config file when the validator is not running in bulk/headless mode).This is now working for headless mode when issues are set in the bulk config file.
The headless version of the validator needs to allow for failure issues to be set based on the needs of whatever program has put its files in the input folder. Since this might be multiple programs at once, each with their own set of issues, the validator needs to be able to set issues on a file-by-file basis.