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 unusual to have for example models.Pet as the name of a definition. It also leads to unusual results from swagger-codegen. I can understand how it can be useful when you actually need to pull definitions from multiple namespaces, but it would be nice to allow swagger generation without the domain namespace in the definitions.
In short, if we reference $ref: '#/definitions/models.Pet there should be some way to have the output in the swagger be just Pet without the namespace.
The text was updated successfully, but these errors were encountered:
It seems unusual to have for example
models.Pet
as the name of a definition. It also leads to unusual results from swagger-codegen. I can understand how it can be useful when you actually need to pull definitions from multiple namespaces, but it would be nice to allow swagger generation without the domain namespace in the definitions.In short, if we reference
$ref: '#/definitions/models.Pet
there should be some way to have the output in the swagger be justPet
without the namespace.The text was updated successfully, but these errors were encountered: