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
It seems to me like the fields in a schema takes precedence whenever a field references a type that already exists. For inline objects, it seems reasonable to generate the type name, but pure references should take priority - no?
I.e it shouldn't create a new type since it has one specified in the component/schema section.
Additional context
I've tried to workaround this with various options, but to no avail. My solution as of right now is to do some pre-processing on the schema, and then fix it with schema wrapping.
I can probably identify and fix this bug if it's declared a bug.
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems to me like the fields in a schema takes precedence whenever a field references a type that already exists. For inline objects, it seems reasonable to generate the type name, but pure references should take priority - no?
To Reproduce
Use this schema:
And generate the schema. The end result will look like this:
Expected behavior
I would expect the schema to look like this:
I.e it shouldn't create a new type since it has one specified in the component/schema section.
Additional context
I've tried to workaround this with various options, but to no avail. My solution as of right now is to do some pre-processing on the schema, and then fix it with schema wrapping.
I can probably identify and fix this bug if it's declared a bug.
The text was updated successfully, but these errors were encountered: