[
https://issues.apache.org/jira/browse/WICKET-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498081
]
Jonathan Locke commented on WICKET-584:
---------------------------------------
I don't agree that "inconsistent" naming of boolean methods is a "problem". It
is perfectly valid to have both isX methods and getX methods that return
booleans (according to the JavaBeans spec). We should be using the naming that
makes sense in English and not be rigorously sticking to isX (which is not now
and never has been a "standard" for boolean values). getAutomaticLinking is
definitely better than isAutomaticLinking, but the best there might be
isAutomaticLinkingEnabled. getCompressWhitespace OTOH is a PERFECTLY VALID
name for this property. In fact, it's the best name for the property and I see
no reason to change it. Truth is there methods are case-by-case. I think we
should close this bug and then reopen new bugs for specific cases of
UNGRAMMATICAL boolean getter methods.
> Use consistent naming for boolean getters
> -----------------------------------------
>
> Key: WICKET-584
> URL: https://issues.apache.org/jira/browse/WICKET-584
> Project: Wicket
> Issue Type: Task
> Affects Versions: 1.3.0-beta1
> Reporter: Thomas Singer
> Assigned To: Jonathan Locke
> Priority: Minor
>
> For example: in ComponentTag there exist isAutoLink(), isOpen(), isClose()
> but in IMarkupSettings there are getAutomaticLinking(),
> getCompressWhitespace() or getStripComments().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
