Implement "inline schemas": ability to add type hints into the type providers' source documents #1447

…ering types from inline schema definitions Ensure backward compatibility + add doc

This means changing inferPrimitiveType to take a UnitsOfMeasureProvier parameter, and return InferedType instead of Type so we can set the units on the returned values in a way that will work with the rest of the code.

where inline schemas types override value-inferred types instead of just adding new types to the list of inferred types. This requires adding metadata on InferedType.Primitive to know if the type should replace other types when merging them. This also requires adding metadata on InferedType.Heterogeneous to keep track of optionality inside an heterogeneous type. (Since we want to be able to transform a heterogeneous type back into a primitive type when the primitive type is supposed to override other primitive types) Preserving optionality in heterogeneous types effectively makes nulls and inline schemas both being considered at the same level of importance when merging.

Not sure why the assert was there, but looking at the similar ConversionsGenerator gives me confidence it shouldn't be here anymore now that we can have units of measure in json...

The existing ones changed to take the BackwardCompatible inference mode. All Json and Xml cases that had value inference enabled have been copied to 3 new cases: one for each value of InferenceMode. The expected content is always the same: enabling inline schemas when no schema is defined in the source file should not change anything to the output.

…nd xml providers)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement "inline schemas": ability to add type hints into the type providers' source documents #1447

Implement "inline schemas": ability to add type hints into the type providers' source documents #1447

Commits on Jul 9, 2022