Usage of ieda refactor

Survive by day and develop by night.
talk is cheap, show me the code,make a better result.

Catalog

summary

I've always wanted to write this usage , I used it before , Only part of it is used , Now outline , When we write the corresponding code according to the business requirements , This is very important .

demand ：

Design thinking

Analysis of implementation ideas

1.Refacot this

Select object , Right click to pop up the suggestion list , Select refactoring .

2.rename

This is simpler , Use naming conventions , Rename it .

3.rename file

Rename the currently selected file

4.change sinnature

Usually it's changing the method , Change method parameters .

5.Edit pro value

Change the attribute value , The directory object does not , May be pro Document has

5.Type m

Type related

5.make static

Action object , Directory does not , Method objects have , It should be to turn the method into static Of .

6.convert to instance method

Turn the method into static Of , and 5 What's the difference ？

7.move class/member

Mobile class directory structure

8.copy class

Will file copy To the specified directory , Local directory failed .

9.safe delete

This is simpler , Safe deletion , File to be deleted file does not exist .

6.Extract

variable

Failed to select file at present , The selected expression should be ：

The extraction expression is constant ：

constant

Filed

Select variable , Property name failed , Similarly, you choose an expression ：

But notice this IEDA Logic is not automatically drawn in , Is to treat the expression as a member variable .

paraeter

Failed to select a single variable name or function list . What should be chosen is the expression ：
Choose the former ：

After refactoring ：

however IEDA There is no corresponding project extraction in logic .

object

Failed to select a single variable name or function list .

method:

Select the code line in the specific method , Extraction method ：

Type parameter

Invalid selection method list .

Method object

Turn the calling method into an internal class and an anonymous class ：

delegate

Usually it is to generate a new class , As a delegate . Called by the delegate object .

interface:

result ：

super class

First choose ：

result ：
Will extract int Attribute and add corresponding extends class ：

inline super class

Select parent class ： After analysis and quotation ：
result ：

Invert bolean

I don't know yet

find and repalce duliate:

pull up member:

pull down member:

Select the corresponding parent class , extract

user inteface:

Choose the method to use , Analyze , Interfaces can be used instead of

inherit from replace

Generate a delegate class , An interface is implemented internally .

remove middlman

The service class has completely become “ A middleman ”, At this point, you should let the client call the entrusted class directly .

wrap method return value

Encapsulation method

encapsulate Fields:

replace temp with query

Replace temporary results with queries

replace constrct with factory

Replace the construction method with the factory method ,
Select the method line ：

replace constructor with build

use builder Pattern construction method ：

genirity

java The generics in , This information is scarce

migrate

transfer , Generally, it provides javaex,junit,swing Migration options ：

interliatelize

online

migrate to anroidRx

Migrate to the corresponding androidRx:

Starting from the basic objects, there are probably so many , The menus that appear for different objects are not the same .

Sequence and method of use

From the perspective of granularity , look down ：
Mainly
1.varibale,constant,filed Wait for the operation
2.function Internal level , Mainly extracting parameters , Object etc. .
3. Choosing multiple lines is method, or method object ( As an anonymous class , Internal class processing )
In fact, it is also different from the extraction menu .

Then it's based on class File level refactoring ：
For a single class ：
1. Delete , Move , Delete etc.
2. A higher level ： Rename, etc .
This part can have operating system management , It only provides another editing entry .

For many categories ： From a design point of view ： Usually 3 individual ：
delagate,interface,superclass,
The first objects to choose are extends,impl Keywords, etc , This part can be realized
For a mature project , Actual letter extends It seems to use more .
For its relationship expansion .

Then there are some pattern Has applied best practices .
Such as builder,factorypattern. Will generate a builder File and call file .

Then there is class lib Level ,
does jar transfer ,class Generic ：
That's right Java Development is basically enough ,

If there is, it is the file conversion between systems, such as ：
Transfer to androidX file .

So far, the analysis is finished .

Expand to achieve

Entry level implementation :

Partial source code implementation .

The source code to achieve

Theory provides the basis . Generally optimized to pattern It's about the floor .

Performance parameter test ：

nothing

References and recommended readings

1. Design patterns .
2. Refactoring patterns .
3. Extract variables .
   4. Reconstruction

Welcome to , Dear brother , If it helps you , A little praise and a little attention ！~