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
Description:
Currently, the library does not support direct serialization and deserialization of Quantity objects. This limitation prevents the use of Quantity as a standalone object in endpoints, resulting in a NullPointerException. An example of the issue is shown below:
java.lang.NullPointerException: Cannot invoke "com.fasterxml.jackson.databind.BeanProperty.getType()" because "property" is null
Improvement Proposal:
I propose adding support for the direct serialization and deserialization of Quantity objects. This would allow developers to use Quantity in RESTful APIs and other contexts without wrapping it in a POJO.
Personal Experience:
I have been exploring the library and its capabilities, and I like what I have seen. However, I believe that we can improve it even more.
Implementation Offer:
If it is acceptable, I am willing to implement this feature. Please let me know if this is okay, and I will be happy to start working on it.
Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered:
Description:
Currently, the library does not support direct serialization and deserialization of
Quantity
objects. This limitation prevents the use ofQuantity
as a standalone object in endpoints, resulting in aNullPointerException
. An example of the issue is shown below:The following exception is thrown:
Improvement Proposal:
I propose adding support for the direct serialization and deserialization of
Quantity
objects. This would allow developers to useQuantity
in RESTful APIs and other contexts without wrapping it in a POJO.Personal Experience:
I have been exploring the library and its capabilities, and I like what I have seen. However, I believe that we can improve it even more.
Implementation Offer:
If it is acceptable, I am willing to implement this feature. Please let me know if this is okay, and I will be happy to start working on it.
Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered: