On Thu, 1 Jun 2017 at 15:27, Gary Gregory <garydgreg...@gmail.com> wrote:
> IMO camel casing is all about words so [text] WordUtils. But why not have a > CamelCaseUtils instead? > > Gary +1. IMO it belongs in TEXT (if anywhere) and we should avoid classes with static methods. Per our other conservation about case conversions, we should carefully specify whether this uses upper- or title-case and how it behaves in different locales. OOI, what is your real world use case for this? Duncan > > On Jun 1, 2017 7:14 AM, "Rob Tompkins" <chtom...@gmail.com> wrote: > > > > > > On Jun 1, 2017, at 10:11 AM, Gary Gregory <garydgreg...@gmail.com> > > wrote: > > > > > > Isn't this kind of stuff or anything camel case supposed to be in > [text] > > > > I’m ok with that path as well. It feels like it’s on the line between the > > two components. Either way, it sounds like you’re not opposed to adding > it > > to a component. > > > > Should it be TextUtils.toCamelCase(String str, char delimiter, boolean > > capitalizeFirstLetter), or WordUtils maybe, if we were to put it in > [text]? > > > > -Rob > > > > > these days? > > > > > > Gary > > > > > > On Jun 1, 2017 7:03 AM, "Rob Tompkins" <chtom...@gmail.com> wrote: > > > > > >> Hello all, > > >> > > >> Folks at my day job have a method that takes in a space delimited > String > > >> (or arbitrarily delimited string for that matter), and returns a camel > > >> cased string. Is there any reason that this shouldn’t be in > > StringUtils? It > > >> feels reasonable to me. What are folks thoughts? > > >> > > >> Cheers, > > >> -Rob > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > >> For additional commands, e-mail: dev-h...@commons.apache.org > > >> > > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >
