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
Is your feature request related to a problem? Please describe.
Some schemas include a member with a common name across multiple definitions, but uniquely defined inside each one.
Currently, this is handled by creating a new definition for each one, with the name being derived from the key name and thus name collisions need to be avoided by adding numbers to later instances.
Describe the solution you'd like
Prefix the model name with the parent model name. This is more readable and provides clearer disambiguation for developers.
Is your feature request related to a problem? Please describe.
Some schemas include a member with a common name across multiple definitions, but uniquely defined inside each one.
synthetic, minimal example
Currently, this is handled by creating a new definition for each one, with the name being derived from the key name and thus name collisions need to be avoided by adding numbers to later instances.
Describe the solution you'd like
Prefix the model name with the parent model name. This is more readable and provides clearer disambiguation for developers.
IE, the model could look like
(note that
BBody
would be currently namedBody1
)Describe alternatives you've considered
Additional context
See DAP for an actual schema with this property, getting to
Body11
The text was updated successfully, but these errors were encountered: