You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Hi @synapseradio! I'm glad you find stdrename useful. :) I can't guarantee a timeline for this, but it sounds easy enough to implement. Should fragments between the first and the last dot be renamed as well or should they be treated as part of the extension?
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 -c
is 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!
The text was updated successfully, but these errors were encountered: