Skip to content
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

Fix for inheritance of abstract properties and ContractResolver that suppresses properties #329

Conversation

markledwich2
Copy link
Contributor

  • fixed logic for which properties should be included in schema
  • added test for custom contract resolver
  • fixed issue with inheritance with an abstract property
  • suppress warnings for xml comments in test project

- fixed logic for which properties should be included in schema
- fixed issue with inheritance with an abstract property
- added test for string type converter as an example of when contract resolver needs to be used
@markledwich2
Copy link
Contributor Author

There is plenty of work to go using the parts from the Json.NET contract resolver that overlap with TypeDescription and other classes. I did the minimal I needed to for my project and I'm not confident in #d7a2429, but I think the unit test should be included as serializing an object to a string using the TypeConverter method is standard for Json.NET.

@RicoSuter RicoSuter merged commit 5a3fc44 into RicoSuter:use-contract-resolver Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants