You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this moment we are using a bit modified approach from REST API, which generates Entity java class and EntityImportView from client json. And then method walks through entity props tree navigated by generated view.
This approach is ok until we meet OneToMany relation with collection of objects. Each object in collection can contains separate set of properties and nesting level. See example below.
Relations between Car and Garage
Car.java
Garage.java
This allow us to make infinite nesting of relations in GraphQL queries
At this moment we are using a bit modified approach from REST API, which generates Entity java class and EntityImportView from client json. And then method walks through entity props tree navigated by generated view.
This approach is ok until we meet OneToMany relation with collection of objects. Each object in collection can contains separate set of properties and nesting level. See example below.
Example 1. Mutation that works fine
json
entity import view
cars
here is collection that can contains nestedgarage
object.Example 2. Mutation below is failed because we can not correctly calculate view for
cars
propertyEach element of collection need to have each own view.
json
entity import view
The text was updated successfully, but these errors were encountered: