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
After thinking this through, I think I agree with the idea that following case should be legal:
public class Value {
public boolean isValue();
public String getValue();
}
even though it could theoretically be problematic. And we probably do not even need configurable feature, unless we find real cases where exception would have been better alternative than simply using 'getValue()'.
EDIT (29-Apr-2022): Just to make it explicit, in above case method getValue() would be selected as THE getter to use (and isValue() ignored).
The text was updated successfully, but these errors were encountered:
(see FasterXML/jackson-core#79 as background)
After thinking this through, I think I agree with the idea that following case should be legal:
}
even though it could theoretically be problematic. And we probably do not even need configurable feature, unless we find real cases where exception would have been better alternative than simply using 'getValue()'.
EDIT (29-Apr-2022): Just to make it explicit, in above case method
getValue()
would be selected as THE getter to use (andisValue()
ignored).The text was updated successfully, but these errors were encountered: