[
https://issues.apache.org/jira/browse/LANG-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203323#comment-13203323
]
Henri Yandell commented on LANG-787:
------------------------------------
Matt: An enum-focused redo of the API for 4.0 to get rid of the 'use a
different method name' approach would be an option. I'd point to the
NumericEntityUnescaper class and its OPTION pattern as a way to have a nice API
that allows future tweaks without screwing with backwards compatibility.
Gary: The if/else problem you list is only valid in the use cases where you
want to reflect the choice to a higher level of the system. I don't think
there's a reason to think that is the majority use case, and even if it is it's
easy to write your own simple function above ours to simplify your code.
> StringUtils.RemoveIgnoreCase desired
> ------------------------------------
>
> Key: LANG-787
> URL: https://issues.apache.org/jira/browse/LANG-787
> Project: Commons Lang
> Issue Type: New Feature
> Components: lang.*
> Affects Versions: 3.1
> Reporter: david cogen
> Priority: Minor
>
> removeStartIgnoreCase() and removeEndIgnoreCase() exist, so why not
> removeIgnoreCase()
> Specifically:
> String removeIgnoreCase(String str, String remove)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
