-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
JsonType.As.EXISTING_PROPERTY
cannot handle multiple types with same class
#716
Comments
Actually, I'm having the same issue with |
I think this is #312, which will be fixed in 2.6.0. So you may want to try 2.6.0-SNAPSHOT to see if that might help. |
As to ordering: it should retain ordering (minus actual property used which will be serialized as the first thing). Although if you have existing property you want to bind to, and you want to specify its ordering, If ordering is otherwise messed up, that would be a bug (type id and object id are exceptions to the rule). |
Yes, looks like #312 is the issue which I didn't come across because I thought it was a problem with As for the ordering, yes that was my expectation which wasn't met. I've tried to reproduce it with unit tests on 2.6.0 but didn't manage to. Maybe I was doing something wrong and misread things; or some chained actions were causing it as lots of object mapping occurs before it happens in the application tests. Thank you! |
This doesn't seem to be a problem when using
JsonType.As.PROPERTY
, so I didn't consider it as an illegal thing to do.And this is the exception message I get:
I'll try to write a unit test when I have time later
P.S.: (If I use
As.Property
, it ignoresJsonPropertyOrder
, and I think it serializes the properties in a somewhat random order. Another issue?)The text was updated successfully, but these errors were encountered: