Skip to content

Backwards compatibility of x-include is broken #495

@lthompson-keysight

Description

@lthompson-keysight

Version information
0.3.34

Describe the bug
x-include is not working any more as a replacement for allOf. It just defines a type for a property and the property name is in the parent object, so this is not very useful. Also, it doesn't work the way it is described in the Model Guide. I have a model that worked fine in 0.1.50, and uses x-include as described in the Model Guide, but 0.3.34 gives the error "missing in internal object.x-include should define within properties"

To Reproduce
Model files attached:
public_api.tar.gz

Expected behavior
Successful compilation of models

Additional context
Backwards compatibility must be maintained. If x-include won't work for field types then we need a new extension for that use case.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions