Better handling for file rename operations (this is NOT full rename refactoring support)

Today if you want to rename a metadata file, you also may need to rename its meta.xml file, update your metadata subscription, and possibly remove the metadata with the original name from the server. When provided, a full rename refactoring will handle this comprehensively, but in the interim it would be useful to have better first-class support in IC for file rename operations that at least do the following:

Rename the companion meta.xml file if present.
Remove the metadata with the old name from the metadata subscription.
Add the metadata with the new name to the metadata subscription.
Deploy the metadata with the new name to the server.
Optionally delete the metadata with the old name from the server.

A stretch goal might be to recognize other files based on the same name and prompt to rename those as well, e.g., layouts for custom objects and such.

Again, this is not intended to be full rename refactoring support. That will come in IC 2.0. Instead this is meant to provide better automated handling of file-level renames when possible to minimize (but not totally eliminate) the amount of manual adjustment required to accommodate for those name changes.

Comments (2)