Presently, if we provide a docx or HTML input spec, we get a JSON output spec which also contains any linting errors encountered (provided they were not explicitly ignored due to command-line flags).
We need to also print these.
This is required to be a replacement for nvme-lint.
We have decided NOT to print each linting issue. Instead, we print a single message indicating one or more linting errors were recorded and direct the user to the JSON output.
Presently, if we provide a docx or HTML input spec, we get a JSON output spec which also contains any linting errors encountered (provided they were not explicitly ignored due to command-line flags).
We need to also print these.
This is required to be a replacement for nvme-lint.