Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
One of the changes to how components are handled in C++ introduced a defect into the original construct over the version 1 schema of the YAML.
The absence of this ID causes a YAML exception.
We should provide handling to support configurations how they were created originally, possibly providing a default/generated ID where one isn't specified, and start laying the foundation for versioned schemas as provided in our Java implementation.
Attachments
Attachments
Issue Links
- is related to
-
MINIFICPP-136 Better handling of required vs. optional fields in config schema v1
- Resolved
- relates to
-
MINIFICPP-66 Provide YAML schema version 2
- Resolved
- links to