Hi! Thank you for writing this library, it's really helpful.
Here's the story behind the request - in a project I'm working on, we have a naming convention where we have [name].[type].[ext].
For example, I'd like to be able to use this util for a file like logger-manager.service.ext, or logger-manager.request-interceptor.ext ( it's a little enterprise-y but it's what I'm working with )
It seems that the extension is currently detected as whatever comes after the first . - the current behavior of stdrename -c is causing this file to become loggerManagerService.ext.
it'd be nice to have dot separators considered separately from other characters. I know this case is a little non-standard, and I appreciate you putting this work up in the first place.
Would be happy to discuss further!
Hi! Thank you for writing this library, it's really helpful.
Here's the story behind the request - in a project I'm working on, we have a naming convention where we have
[name].[type].[ext].For example, I'd like to be able to use this util for a file like
logger-manager.service.ext, orlogger-manager.request-interceptor.ext( it's a little enterprise-y but it's what I'm working with )It seems that the extension is currently detected as whatever comes after the first
.- the current behavior ofstdrename -cis causing this file to becomeloggerManagerService.ext.it'd be nice to have dot separators considered separately from other characters. I know this case is a little non-standard, and I appreciate you putting this work up in the first place.
Would be happy to discuss further!