New herb, complement a herb or use some market lib to transforms and conversions? about herbs HOT 6 OPEN

Already exists so much libs that do it, I'm not sure build a new lib to do that is a good idea

I agree with you, but the proposal is to build herbs with minimal dependencies. And the idea is just to remove the conventions that already exists in other herbs libs and reduce code duplicity

from herbs.

Already exists so much libs that do it, I'm not sure build a new lib to do that is a good ideia

from herbs.

I think it would be ok to have a new herb/lib just for that.

Since many herbs and glues allow custom naming convention, I think it could be useful.

Just to make it clear: the propose of such lib would be to have string transformations (camelcase, for example). is that right?

from herbs.

I think it would be ok to have a new herb/lib just for that.

Since many herbs and glues allow custom naming convention, I think it could be useful.

Just to make it clear: the propose of such lib would be to have string transformations (camelcase, for example). is that right?

For now, I think the main proposal is work with transformations, not only pure string, but if necessary work with subtypes like json, XML, hexadecimals etc

from herbs.

not only pure string, but if necessary work with subtypes like json, XML, hexadecimals etc

it's still not clear for me what the use cases here beyond string transformation (camelcase, for example) for naming conventions. we also have to ask ourselves if this scope is big enough for a new lib

from herbs.

I dont agree to create a new glue to do transformations, it's not a big resource/feature, it's could to be implemented inside some existent lib ooooor we could to use an existent open source lib

from herbs.