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
GetClosestMatchProperty makes deserialization of backingfield with getter fail #16
Comments
Ok, it does not look like it has anything to do with GetClosestMatchProperty()... Hmm... I'm investegting further, it looks like two different, but similar behaviours I've encountered. |
Ok. I've encountered two different issues. The Second issue is actually related to GetClosestMatchProperty, when you have a json document with a property that is no longer present in the new representation of the .net class (migrating documents from a Raven database). The test for this is:
Would you like a pull request with the failing tests? Or is here ok? |
If you even consider them bugs, that is :) The first one seems to be solvable by some settings - when I get the serializer through RavenDb the issue goes away. But I can't figure out why. The second one is happening, because I try to deserialize with another contract resolver than I serialized with, so it might not be such a valid case. But it would still be nice to be able to disable the fallback to case insensitive properties and just ignore if a property is missing. |
I believe you could override this by creating your own contract resolver. |
@asgerhallas did you implement your own contract resolver? (I need case sensitive deserialization) |
Hi
The following test shows what might be a bug:
Would it be possible to make an option to disable the case insensitive property name match?
Regards, Asger
The text was updated successfully, but these errors were encountered: