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
Error occurs when $ref refers to a property of another object.
This feature can be useful because it allows you to edit the properties of an object in one place (especially when using different models for requests).
Error generating code: error generating type definitions: error generating Go types for component schemas: error converting Schema CreateSample to Go type: error generating Go schema for property 'field': error turning reference (#/components/schemas/Sample/properties/field) into a Go type: unexpected reference depth: 6 for ref: #/components/schemas/Sample/properties/field local: true
The text was updated successfully, but these errors were encountered:
Interesting! I think this isn't a use-case we expected, but I can see why it's useful.
I wonder if a fix for this is best gated behind a flag to allow folks to opt-in to the changes, but I'd be happy with there being support added for this, and would review a PR that's raised for it!
In my opinion, this check doesn't seem to be providing much value, and
we've got a few folks requesting this be disabled.
Instead of gating this behind a feature flag, we'll just remove it.
Closes#1348.
Issue
Error occurs when $ref refers to a property of another object.
This feature can be useful because it allows you to edit the properties of an object in one place (especially when using different models for requests).
Example
Output
Error generating code: error generating type definitions: error generating Go types for component schemas: error converting Schema CreateSample to Go type: error generating Go schema for property 'field': error turning reference (#/components/schemas/Sample/properties/field) into a Go type: unexpected reference depth: 6 for ref: #/components/schemas/Sample/properties/field local: true
The text was updated successfully, but these errors were encountered: