Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow existence of overlapping getter, is-getter #238

Closed
cowtowncoder opened this issue Jun 7, 2013 · 0 comments
Closed

Allow existence of overlapping getter, is-getter #238

cowtowncoder opened this issue Jun 7, 2013 · 0 comments

Comments

@cowtowncoder
Copy link
Member

cowtowncoder commented Jun 7, 2013

(see FasterXML/jackson-core#79 as background)


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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant