Based on the defined schemas, a "table-of-contents" file may contain references to "in-network" and "allowed-amount" files. An "in-network" file may contain references to "provider-reference" files. These references are collected during validation. When these references exist, show the user the list of references and ask if they want to validate those files. If they say yes, download and validate the referenced files. When an output file is specified, the results for all files are included in the output.
This PR also includes some refactoring of existing functions into SchemaManager and DockerManager classes. The goal of this refactoring is to reduce code duplication and move logic out of the main command-handling functions. There is definitely more refactoring that can be done, but the amount in this PR feels like a good start.
Based on the defined schemas, a "table-of-contents" file may contain references to "in-network" and "allowed-amount" files. An "in-network" file may contain references to "provider-reference" files. These references are collected during validation. When these references exist, show the user the list of references and ask if they want to validate those files. If they say yes, download and validate the referenced files. When an output file is specified, the results for all files are included in the output.
This PR also includes some refactoring of existing functions into
SchemaManagerandDockerManagerclasses. The goal of this refactoring is to reduce code duplication and move logic out of the main command-handling functions. There is definitely more refactoring that can be done, but the amount in this PR feels like a good start.