You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a feauture in Yasson that check number values and tries to figure out if the values does "fit" IEEE754 double precision range or not. Based on the result the number is written either as JSON string or JSON integer. This proves to be a wrong approach causing to break any schema and making documentation of REST APIs tricky.
For now this feauture should be removed, after jakartaee/jsonp-api#176 is accepted and released, Yasson should support similar parameter configuration to pass it to jsonp, which in turn would know how to handle these types properly.
There is a feauture in Yasson that check number values and tries to figure out if the values does "fit" IEEE754 double precision range or not. Based on the result the number is written either as JSON string or JSON integer. This proves to be a wrong approach causing to break any schema and making documentation of REST APIs tricky.
For now this feauture should be removed, after jakartaee/jsonp-api#176 is accepted and released, Yasson should support similar parameter configuration to pass it to jsonp, which in turn would know how to handle these types properly.
[1] jakartaee/jsonb-api#112
[2] jakartaee/jsonp-api#160
[3] https://github.com/cyberphone/I-JSON-Number-System#java-json-b
The text was updated successfully, but these errors were encountered: