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
Currently creating a TypeInformation of a type will recurse into its properties without checking if the type was already encountered.
This is problematic for types like classes which may contain themselves.
Propose Solution
The TypeStore could be extended to resolve this problem, introducing references when parsing types which were already encountered.
Note: In the context of ApodiniOpenAPI, the OpenAPI exporter would probably need to ship support for Polymorphism. We countering such self references types (e.g. a tree) where no optionals are involved, you would typically introduce a terminating node in order to not get into an endless cycle. This would need to be documented.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently creating a
TypeInformation
of a type will recurse into its properties without checking if the type was already encountered.This is problematic for types like classes which may contain themselves.
Propose Solution
The
TypeStore
could be extended to resolve this problem, introducing references when parsing types which were already encountered.Note: In the context of ApodiniOpenAPI, the OpenAPI exporter would probably need to ship support for Polymorphism. We countering such self references types (e.g. a tree) where no optionals are involved, you would typically introduce a terminating node in order to not get into an endless cycle. This would need to be documented.
The text was updated successfully, but these errors were encountered: