Daniel,
I just cloned what's done on PR 450. I haven't been able to do much on mine
(or yours) yet, I will devote some time Sunday to revising my PR 528 and
looking at your PR 450 with more detail.
I am thinking the existing toCamelCase(String, boolean, char[]) might be
better depreciated and its
Stephan,
On that note, I worked on the initial implementation for PR 450, and had to
pause for work but am planning to resume soon, but definitely contribute
and/or provide any thoughts as it's definitely a big change from the
current CaseUtils.
Regards,
Dan
On Wed, Apr 10, 2024, 9:20 PM Stephan
Gary, thank you for your response.
I initiated the pull request (#528) and already received some very
constructive feedback from user mbenson.
I am modifying the code to contain fewer methods that may be externally
modified by a user, if something as simple as .toLowerCase() is required.
I also n
OK, I will initiate a PR.
Some of the added methods will be more useful than others.
The PR will come from speters33w.
Thank you,
Stephan Peters
On Tue, Apr 9, 2024 at 5:31 PM Gary Gregory wrote:
> Hello Stephan,
>
> The best way to see what you are proposing is a PR, it's a bit painful to
> se
Hello Stephan,
The best way to see what you are proposing is a PR, it's a bit painful to
see differences otherwise, at least for me.
That said anything new should solve a real world use case, not merely
something that might be useful (or not) 😉
I think seeing tests in a PR will help clarify what
