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
Here is an example of a Pojo that would cause problem.
@Getter
class MyClass {
private String aField;
}
From what I understand, Lombok will generate the method .getAField() but OpenPojo will look for a getter named .getaField() (notice the different case).
From what I can see in the code, it's made explicit (see AttributeHelper class) but I don't understand this choice (maybe there is some standard for POJOs that Lombok doesn't follow and I'm not aware of?). Is there any reason why we should keep this if clause? If yes, do you think it would be possible to make OpenPojo to check for the presence of either .getAField() or .getaField()?
Thank you for this nice library.
The text was updated successfully, but these errors were encountered:
Well, I just found out the following link that kind of explain my problem: the answer seems to be "there is some standard I was not aware of". Some framework like Jackson offer the possibility to bypass that in a way (see this link). Would it be desirable to implement such a possibility?
Here is an example of a Pojo that would cause problem.
From what I understand, Lombok will generate the method
.getAField()
but OpenPojo will look for a getter named.getaField()
(notice the different case).From what I can see in the code, it's made explicit (see
AttributeHelper
class) but I don't understand this choice (maybe there is some standard for POJOs that Lombok doesn't follow and I'm not aware of?). Is there any reason why we should keep thisif
clause? If yes, do you think it would be possible to make OpenPojo to check for the presence of either.getAField()
or.getaField()
?Thank you for this nice library.
The text was updated successfully, but these errors were encountered: