Java boolean getters "is" vs "are"

java naming-conventions boolean
kodai picture kodai · Oct 18, 2012 · Viewed 29.8k times · Source

I know that the convention in Java for boolean getters is include the prefix "is". 

isEnabled
isStoreOpen

But what if the subject is plural? That is, what if instead of wanting to know if a store is open, I wanted to know if all the stores are open?

isStoresOpen() doesn't make sense in English.

I'm tempted to write getters like:

areStoresOpen
areDogsCute
areCatsFuzzy

And I think that would make sense, but I've been told by others that I should just suck it up and abandon subject verb agreement and use isStoresOpen, isDogsCute, isCatsFuzzy.

Anyway, what should I do for boolean getters which operate on a plural subject?

Answer

satur9nine picture satur9nine · Mar 14, 2014

How about having decent enough english and following Java standard:

isEveryStoreOpen() or isEachCatCute()

When in doubt of the right word I always like to hit up the thesaurus.

Related questions

Valid JavaBeans names for boolean getter methods

I know most variable names will work with "is", such as isBlue(), but is "has" also a valid prefix, like hasProperty()?

Read More
Java Interfaces/Implementation naming convention

How do you name different classes / interfaces you create? Sometimes I don't have implementation information to add to the implementation name - like interface FileHandler and class SqlFileHandler. When this happens I usually name the interface in the "normal" name, …

Read More
Interface naming in Java

Most OO languages prefix their interface names with a capital I, why does Java not do this? What was the rationale for not following this convention? To demonstrate what I mean, if I wanted to have a User interface and …

Read More