I noticed that the value of PaymentResponse.isCancelable is always false event if the value of json field is true.
Since you are using Lombok I decided to analyze the class file:
public class PaymentResponse {
private boolean isCancelable;
public boolean isCancelable() {
return this.isCancelable;
}
public void setCancelable(boolean isCancelable) {
this.isCancelable = isCancelable;
}
}
Considering that the name of json field is : "isCancelable": true the name of the setter doesn't fit into Jackson serialization mechanism because, as I can imagine, it is trying to find the setter method called setIsCancelable rather than setCancalable
and because such method doesn't exist, the setter is never called.
The way how setters are generated it's a specific behavior and apparently, Lombok team doesn't consider it as a bug,
it's just a design decision, however, it's affecting your library
I noticed that the value of
PaymentResponse.isCancelable
is always false event if the value of json field is true. Since you are using Lombok I decided to analyze the class file:Considering that the name of json field is :
"isCancelable": true
the name of the setter doesn't fit into Jackson serialization mechanism because, as I can imagine, it is trying to find the setter method calledsetIsCancelable
rather thansetCancalable
and because such method doesn't exist, the setter is never called. The way how setters are generated it's a specific behavior and apparently, Lombok team doesn't consider it as a bug, it's just a design decision, however, it's affecting your library