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.
Since head schema is not exposed to users directly, it is not obvious that docsting will be copied to all generated schemas. And this docstring is shown in swagger docs. Also I'm not sure, that cadwyn user want same description for all versions.
Describe the solution you'd like
I see different options to solve it
Disable copy of docstring
Add warning about it on code generation
Add setting to disable it
Migrate docstrings
Additional context
Request come from a case on my current job. We added internal docstring to head schema and it was exposed in swagger
The text was updated successfully, but these errors were encountered:
Could you explain a use case where the docstring would need to be migrated or be different in between the internal and external schemas? It is not a breaking change.
Is your feature request related to a problem? Please describe.
Since head schema is not exposed to users directly, it is not obvious that docsting will be copied to all generated schemas. And this docstring is shown in swagger docs. Also I'm not sure, that cadwyn user want same description for all versions.
Describe the solution you'd like
I see different options to solve it
Additional context
Request come from a case on my current job. We added internal docstring to head schema and it was exposed in swagger
The text was updated successfully, but these errors were encountered: