Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Renaming Properties, Methods and Variables

DZone's Guide to

Renaming Properties, Methods and Variables

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.

Have you ever written some code and named something one thing only to realize that it should be named something else?

If you haven’t you haven’t been programming for very long.  Maybe you started a new job and you spent two weeks writing code using your previous employer’s naming conventions only to find out that this employer expects things to be named slightly differently.

So now you not only have the item named incorrectly, but you’ve referenced it from other files, so it isn’t a simple matter of just giving it a new name.  No, the code that is referencing it has to be changed as well.  So what are you going to do?

In the “old days” we’d change the name, recompile and fix all the references.  But now there is a much easier way to fix this problem.  All you need to do is to right-click on the property, method, or variable and select “Refactor” > “Rename…” from the context menu.

This will bring up a dialog box where you can give the item a new name and optionally select if you’d like to preview the changes, make changes in your comments (that are also referencing this variable name) and search for it in strings.

Press “OK” to continue and all of the names of the item as well as all of the references to that item will automatically be changed for you.

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}