[
https://issues.apache.org/jira/browse/JOHNZON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575034#comment-17575034
]
Romain Manni-Bucau commented on JOHNZON-370:
--------------------------------------------
done no?
> Include class, property, type and json value in mapping exceptions
> ------------------------------------------------------------------
>
> Key: JOHNZON-370
> URL: https://issues.apache.org/jira/browse/JOHNZON-370
> Project: Johnzon
> Issue Type: Improvement
> Reporter: David Blevins
> Priority: Major
> Fix For: 1.2.19
>
>
> Ideally, mapping exceptions that pertain to setting properties give
> information that can help users find the java side, e.g:
>
> {code:java}
> public static class Widget {
> private Color[] arrayOfObject;
> {code}
> And the json side:
>
> {code:java}
> [{"red": 255, "green": 165, "blue":0},{"red": 0, "green": 45,
> "blue":127}]{code}
> Then when things do not match up, I have enough reference points to see and
> resolve the issue.
> Ideally as well this information would be very brief and avoid printing
> entire class names, packages and all as it does reduce readability
> significantly by burying the exception text. Enough short context clues is
> enough for users to reasonably be enabled to find issues. Most will see the
> issue quite quickly given a few hints.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
