-
Notifications
You must be signed in to change notification settings - Fork 96
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
Displayed model schema should match the EDM Model #59
Comments
Thanks Harrison, I'll checkout your sample. |
@bigred8982 Fix is available in v2.12.1. Give it a shot and let me know if you find any issues. Thanks! |
The casing has definitely been taken care of. I discovered a related issue. The model may still not match what is in the EDM is you customize the EDM model with ignored properties. I haven't had the chance to investigate the origin of this specific issue myself, but I did update a sample project to demonstrate it. https://github.com/bigred8982/Swashbuckle.OData/tree/property_casing_sample. The Thanks for all the hard work! |
Hey @bigred8982, you bet! Ignored properties issue is fixed in v2.12.3. Thanks for the heads up! |
You're the best! Thanks!!
|
When using automatic property name conversion via the EnableLowerCamelCase() method on the ODataConventionModelBuilder, the models displayed in the Swagger UI do not match the models in the payload.
For example, the C# model will have a property called 'Id' The service is returning the property as 'id' in the payload. The Model and Model Schema sections are displaying the C# property name in Pascal case.
I have prepared an example to illustrate the issue. Please refer to Swashbuckle.OData.Sample project in the branch below:
https://github.com/bigred8982/Swashbuckle.OData/tree/property_casing_sample
The text was updated successfully, but these errors were encountered: