The existing OEM manager schema needs broken out into the appropriate resource schemas for pid controllers fan controllers, and stepwise controllers, with appropraite entity types for each.
When James first built this schema, it was the only non-trivial OEM schema we'd ever built, and it has mistakes, and issues that have haunted us ever since.
Ideally, when this is implemented, we'd leave a compile time option to allow the old behavior for some time, to avoid completely breaking things.
Other issues with the schema:
It declares everything within a collection block, rather than making it an actual resource collection. This makes filtering (when we have it) fail, given how it's organized.
All of the schemas are Complex type, instead of Entity type. This means that the properties within them are maleable. In practice, they're not maleable, and we should have concrete types for each.
The existing OEM manager schema needs broken out into the appropriate resource schemas for pid controllers fan controllers, and stepwise controllers, with appropraite entity types for each.
When James first built this schema, it was the only non-trivial OEM schema we'd ever built, and it has mistakes, and issues that have haunted us ever since.
Ideally, when this is implemented, we'd leave a compile time option to allow the old behavior for some time, to avoid completely breaking things.
Other issues with the schema: