jsonschema-tools materializes current.yaml JSONSchema files with $refs, etc. into dereferenced and versioned .yaml and .json files.
I just learned that the ordering of the fields in JSONSchema objects is different between the two different outputs. For dynamic languages like python or javascript, the order of the fields don't matter. However, for strongly typed systems like Java or SQL systems, field ordering can matter.
Deserializing the materialized yaml or json schema files should result in the exact same document, but at the moment, it won't.
To fix:
- jsonschema-tools should ensure consistent field ordering in materialized files.
- all materalized schemas in schema/event/{primary,secondary} repositories need to be rematerialized to ensure the existent schemas have consistent ordering.