Fix use of `DynamicTypeResolver` during deserialization.
Previously the type resolver would only be able to return the static type because the object constructed by the factory was not passed into the type descriptor.
See the added tests for a couple of use cases.
I'm not sure that this change is correct. What are you trying to achieve ? I don't think that the type inspectors should use the type resolver at that point.
I'm not sure that this change is correct. What are you trying to achieve ? I don't think that the type inspectors should use the type resolver at that point.
We're trying to achieve a couple of things (both demonstrated in the added tests):
- Deserialize properties that aren't present in the expected/static type but are in the instantiated type.
- Deserialize properties which are get-only in the expected/static type but have setters in the instantiated type.
This PR appears to be abandoned, it's over a year old. I'm going to close it.
That's fine; I'm no longer working on the project utilizing YamlDotNet. The project moved forward with a fork that had these changes.