We can leverage the transport that the jay command provides instead of creating this all from scratch when there is a lot in command with jay. It is going to be a lot more efficient to implement the bulk rename as a new sub command of jay.
Because the bulk rename tool could be very comprehensive in its own right, we could introduce another sub level in the command structure. So we could have a structure that requires invocation like this:
jay rename move
where move is a sub-command of rename
In reality, we want to be more concise so this will probably be defined as:
jay rn move
A bulk renamer does not lend itself to sprint, so it will only ever be a walk type of command.
The bulk rename will be a better version of rename-many command implemented in RexFS, which has been retired. There are still some outstanding issue on that project and there were a few design mistakes that I don't want to be replicated here.
The flags and sub-commands defined for 'jay rn' should be inspired by not limited/restricted by rexfs. An initial implementation plan can be derived from what rex-fs provides.
We can leverage the transport that the jay command provides instead of creating this all from scratch when there is a lot in command with jay. It is going to be a lot more efficient to implement the bulk rename as a new sub command of jay.
Because the bulk rename tool could be very comprehensive in its own right, we could introduce another sub level in the command structure. So we could have a structure that requires invocation like this:
where move is a sub-command of rename
In reality, we want to be more concise so this will probably be defined as:
A bulk renamer does not lend itself to sprint, so it will only ever be a walk type of command.
The bulk rename will be a better version of rename-many command implemented in RexFS, which has been retired. There are still some outstanding issue on that project and there were a few design mistakes that I don't want to be replicated here.
The flags and sub-commands defined for 'jay rn' should be inspired by not limited/restricted by rexfs. An initial implementation plan can be derived from what rex-fs provides.