Closed elray1 closed 1 year ago
😳 Very strange! That should indeed be failing. Will investigate!
Turns out additional properties are just ignored by default and additionalProperties; false
is required to explicitly throw an error https://json-schema.org/understanding-json-schema/reference/object.html#additional-properties
Fixed in the schema via https://github.com/Infectious-Disease-Modeling-Hubs/schemas/pull/51
The tasks.json file in the example-simple-forecast-hub currently has a
target_metadata
block that is in the wrong location, here. That block is nested within the"output_type"
block, but I think it should not be there. Note that theoutput_type
specification in the schema file does not includetarget_metadata
as a valid output type.However, running
hubUtils::validate_config
yields a passing result: