Generated examples imply that deep insert or update is supported

[tsg2k2]

For entity defined as

<EntityType Name="Other" BaseType="nsp.Base">
    <NavigationProperty Name="Derived" Type="nsp.Derived" Partner="Others" Nullable="false"/>
</EntityType>

Generated sample for POST includes Others

{
  "Name": "string",
  "SomeProperty": "string",
  "Others": [
    {
      "Name": "string"
    }
  ]
}

It should only happen if deep insert/update capabilities are supported

[ralfhandl]

@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?

[tsg2k2]

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

[ralfhandl]

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