-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add decorator to allow specification of the schema type name #981
Comments
Would you like to create a PR for this? |
May I try? |
@libertysoftware - go for it! I likely won't have time to get to it in the near future. |
See the PR here |
On review, I'm thinking And as we're adding that, we should add the other properties that are tied to the schema object that can't be set via annotations on the properties:
After creating this issue, I found that I really wanted at least |
Hello, what's the status of this issue? |
The original feature is implemented in my fork but the additional requested features not. I think my PR is still not merged. |
Removed my comment from #983 in case it was blocking getting your change merged @radacovsky . Makes sense that we could file separate tickets for the other requested features. |
Let's track this here #983 |
I'm submitting a...
Current behavior
The Open API schema type name is the same as the type name.
Expected behavior
Add a decorator to allow specification of a schema type name that is different from the type name.
For example:
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Type names often have suffixes such as
Entity
orDto
that represent internalimplementation choices. Allowing explicit specification of the schema type name
would avoid leaking these choices into the public interface.
Environment
The text was updated successfully, but these errors were encountered: