On Wed, Aug 9, 2023 at 11:36 PM Daniel Watson <dcwatso...@gmail.com> wrote: > > Meant to add... > > The reason I would favor exceptions is that the underlying implementation > can be easily customized. If the user needs to allow non alphanumeric > characters there is a boolean flag in the underlying abstract class > (AbstractConfigurableCase) that will simply turn that validation off.
This is another point, but customizability is a bug, not a feature. I don't want to guess what the method might be doing based on what flag was set where. I want camel case to mean one thing and one thing only. Ditto snake case, pascal case, and any other formats. Possibly there's a reason to add additional subclasses, but the CamelCase/SnakeCase/KebabCase classes should not emit different strings depending on how they're configured. The public API should be a pure function, not an object. -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
