Hi Gary,
On 4.12.2024 12:44, Gary Gregory wrote:
The StringUtils methods return a mix of null and "" for each method on null
input. Each method does one of the following:
- null out for null in
- "" out for null in
- null for null and "" for ""
- throw an NPE
We definitively need to put some
Hi,
In my opinion it would be nice if all the methods do the same for the same
null or empty string input and would be consistent, but...
I won't change the existing API in the current 3.x version.
So I think we should fix them only in 4.0.
However, we should fix it in the Strings class, before it
Hi all,
The StringUtils methods return a mix of null and "" for each method on null
input. Each method does one of the following:
- null out for null in
- "" out for null in
- null for null and "" for ""
- throw an NPE
The newer class Strings does the same as it backs StringUtils.
Should we:
-
I don't see a 2.x needed either for now.
Please do clean up/reduce the newly introduced methods as you see fit. We
don't want to make the public/protected API possibly confusing with too
many choices. A small risk perhaps.
Gary
On Wed, Dec 4, 2024, 4:21 AM Claude Warren wrote:
> The only other
The only other thing I can think of is to drop some of the retrieval
patterns. We have getOption() with String, char, Option, OptionGroup as
arguments and then that duplicated across getParsedOption, getOptions, and
getParsedOptions. I think we can limit that to Option and Group arguments.
But o
