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
The generator will currently place all generated model files in the same folder. This doesn't work well with larger models that may support different versions of the same API (requiring all model files to have unique names). The translation of schema names to model names also does a significant amount of character substitution, changing case etc. of the schema names, which further separates the generated code from the assigned schema name.
will generate a SomeNamespaceModel class file in the io.swagger.model namespace instead of a Model class in some.namespace
Because there's a significant amount of conversion of model names by legacy (transliterating _. etc to title case.
I propose to add a new flag to support generating fully-qualified names: useFqn
The text was updated successfully, but these errors were encountered:
The generator will currently place all generated model files in the same folder. This doesn't work well with larger models that may support different versions of the same API (requiring all model files to have unique names). The translation of schema names to model names also does a significant amount of character substitution, changing case etc. of the schema names, which further separates the generated code from the assigned schema name.
For example the following
will generate a
SomeNamespaceModel
class file in theio.swagger.model
namespace instead of aModel
class insome.namespace
Because there's a significant amount of conversion of model names by legacy (transliterating _. etc to title case.
I propose to add a new flag to support generating fully-qualified names:
useFqn
The text was updated successfully, but these errors were encountered: