An empirically-common use case is for someone to receive a bare report.json and then need to generate the relevant human-friendly artifacts from it. This PR supports this use case by making explicit specification of a configuration optional when calling make_artifacts. When not specified, the configuration embedded within the provided report(s) will be used to specify the artifacts to be generated.
An empirically-common use case is for someone to receive a bare report.json and then need to generate the relevant human-friendly artifacts from it. This PR supports this use case by making explicit specification of a configuration optional when calling make_artifacts. When not specified, the configuration embedded within the provided report(s) will be used to specify the artifacts to be generated.