Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
From: PascalSchumacher <git@git.apache.org>
To: issues@commons.apache.org
Reply-To: issues@commons.apache.org
References: <git-pr-221-commons-lang@git.apache.org>
In-Reply-To: <git-pr-221-commons-lang@git.apache.org>
Subject: [GitHub] commons-lang issue #221: Add IsAllEmpty and isAllBlank methods
Content-Type: text/plain
Message-Id: <20161206202114.27165E0159@git1-us-west.apache.org>
Date: Tue,  6 Dec 2016 20:21:14 +0000 (UTC)
archived-at: Tue, 06 Dec 2016 20:21:16 -0000

Github user PascalSchumacher commented on the issue:

    https://github.com/apache/commons-lang/pull/221
  
    >I vote strongly for is* method naming. That's the convention for Java methods of this type, even if it slightly upsets the English ear.
    
    Then let's keep is* names.
    
    >Other topic: what do you think of the handling of empty array or null as a single parameter? Is it right to return true in these cases?
    
    I'm not sure what the behavior should be in these cases. @dmjones500 / anybody else: any opinions on this?
    

---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---