-
Notifications
You must be signed in to change notification settings - Fork 678
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
[Question] Use custom serializer to serialize objects? #170
Comments
Hey there Swashbuckle 5.0 honors Json attributes out-of-the-box. It's currently in alpha and is available as a Nuget pre-release:
It does introduce some significant changes including a move to Swagger 2.0 and subsequent changes to the config API. If you're only using the UI, it should remain relatively unchanged, If you have other consumers of the raw Swagger document, you'll need to ensure they can accept Swagger 2.0. Finally, if you're using the Swashbuckle config API extensively, you should take a look at the transition guide here - https://github.com/domaindrivendev/Swashbuckle/tree/swagger_2.0#transitioning-to-swashbuckle-50 Other than that, the upgrade should be relatively seamless. Complete docs for the alpha version are available here - https://github.com/domaindrivendev/Swashbuckle/tree/swagger_2.0 Let me know how it goes ... |
Great, thanks for the swift response. It definitely resolves my issue. |
This is fixed! |
An answer to this question "But is there way we can plug in a different serializer? Thanks again." would be great |
Swashbuckle seems to serialize objects to camel case, I use NewtonSoft lib to serialize objects in the app which has an attribute [JsonProperty(name="")] and these are used in serialization. Is there a way I can customize Swashbuckle to use the same api used in the application?
The text was updated successfully, but these errors were encountered: