Open mcliedtke opened 7 years ago
Unfortunately never looked into this. Assuming you think it is a valid issue (I am not familiar enough with Ion's type system unfortunately), would probably make sense to add test case in repo, at least (under failing
so as not to break builds).
Ran into a strange issue with deserializing wrapper/value classes when the content of the IonValue is suppose to be a struct. Some test cases are below. The issue is shown at the bottom of the test below:
mapper.readValue("{ a: b }", TestValueType.class);
. This gets read as an ion symbol 'b' instead of an ion struct { a: b } and I believe it's because of the code here that steps into the struct before yielding to the deserializer?Not sure if this is the correct analysis or what the proper course of action should be if it is correct. Any ideas?