Rename dialog for a class or an interface
Use this dialog to rename a class or an interface.
In addition to renaming the class or the interface itself, DataSpell can also look for the usages of the class or the interface name. If found, the changes you are making to the class or the interface name can also be applied to these usages.
The usages are assigned to different categories which correspond to the options which you can turn on and off.
Note that regardless of the options selected, the search scope (places where you search for the name occurrences) is always limited to the current entity (for example, a file, or a class) and the entities that the current one depends on.
Item | Description |
|---|---|
Rename <class or interface> and its usages to | Specify a new name for the class or the interface. |
Search in comments and strings | If this checkbox is selected, DataSpell will look for occurrences of the class or the interface name within comments and string literals in your source code files. |
Search in loaded sources | If this checkbox is selected, DataSpell will look for occurrences of the class or the interface name within downloaded object sources. |
SQL Script | The statement to be run to rename the table or column. If necessary, you can edit the statement right in this pane. |
Refactor | Execute the statement and make associated changes right away. |
Preview | Preview potential associated changes prior to executing the statement. |
Search for text occurrences | If this option is on, DataSpell will look for occurrences of the class or the interface name in the files that don't contain source code. These may be the text files, properties files, HTML files, documentation files, and so on. |
Scope | Use this option to set a scope for the Rename refactoring. For example, you can limit the refactoring to only recently changed files, or to only open files, and so on. You can also create a custom scope that you can either share or keep local. |