-
Notifications
You must be signed in to change notification settings - Fork 55
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
Using JsonCustomConverter causes Expected type to be undefined #75
Comments
The error message should be indeed improved. It cannot determine the expected type, but indeed we should fix this to show I don't understand the logic above, there are maybe some things to correct:
What is |
@andreas-aeschlimann should be datA not datE - just copy paste error of mine. If you are ok with this let me know, I can send you fix or just allow me to push something on separate branch so I can open pull request to master. |
@andreas-aeschlimann TODO: /*170*/ } else {
/*171*/ jsonPropertyMappingOptions.expectedJsonType = conversionOption;
/*172*/ } |
Line 171 is correct actually. If you provide a custom converter, the expected type would be the one given in the methods of the converter. The problem is somewhere else: The error that you throw is caught by However: I planned to add custom errors in the next big version to improve error handling. This might help in this case. |
Example:
Will thorw error message:
I expect to be able to determine Expected type because in above case it is undefined
The text was updated successfully, but these errors were encountered: