Circularity between object and interface type definitions #205
The following circularity is problematic for users:
In the above example, the
In this case,
The situation is further complicated when schema types are not defined as class members. For example, there is no direct way to resolve the circularity above if the same schema is defined within a method body.
There is no idiomatic way to solve this issue. Looking at the tests, types are defined as class members, leading the user to conclude that that is the only way to define a schema where interface/object relationships must be defined.
This is fine, but not good. To address this issue: