Generated examples imply that deep insert or update is supported about odata-openapi HOT 3 OPEN

@tsg2k2 The tool currently makes the simplifying assumption that

• deep insert is always possible
• deep update is never possible (because it was only added in V4.01, which is not finalized yet)

This works for most services.

The tool currently produces components from the types and reuses these in all operations. Assume A -> B -> C, then the insert structure of A references the insert structure of B, which references the insert structure of C, allowing deep insert of A with B with C.

Full support for deep insert/update capabilities and expand restrictions would require a more complicated approach: assume B allows deep insert of C, and A allows deep insert of B but not C. This would require completely different insert structures for A and B.

Thoughts?

from odata-openapi.

I think that good start would be to take into account deep insert capability. It's is good enough for many simple use cases.

from odata-openapi.

Since version 0.9.0 deep insert and deep update is only implied for containment navigation properties.

from odata-openapi.