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
{{ message }}
This repository has been archived by the owner on Jun 10, 2021. It is now read-only.
Sometimes I want to modify all instances of a particular string in an Objective-C/Swift codebase. At Facebook, that means --extensions=h,m,mm,swift,BUCK,plist.
Typing those out is a pain--instead, it might be cool to have "extension groups", or aliases for a list of extensions. For example, if we defined a group called ios, these two would be equivalent:
--extensions=h,m,mm,swift,BUCK,DEFS,plist
--extensions=ios
Since ios means different things to different teams, maybe one should be able to register their own custom groups, instead of codemod making a decision as to what ios means for everyone.
Not sure if this is a good idea, as it might just be adding a complex feature without a great need to--thoughts? 🙌
The text was updated successfully, but these errors were encountered:
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
I don't personally have a use for this feature, but I could see it being useful. Overall I think it's too much complexity for a niche use-case. Anyone else think this could be helpful?
Sometimes I want to modify all instances of a particular string in an Objective-C/Swift codebase. At Facebook, that means
--extensions=h,m,mm,swift,BUCK,plist
.Typing those out is a pain--instead, it might be cool to have "extension groups", or aliases for a list of extensions. For example, if we defined a group called
ios
, these two would be equivalent:Since
ios
means different things to different teams, maybe one should be able to register their own custom groups, instead of codemod making a decision as to whatios
means for everyone.Not sure if this is a good idea, as it might just be adding a complex feature without a great need to--thoughts? 🙌
The text was updated successfully, but these errors were encountered: