You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the 21-line statement in class B is selected to perform extraction method refactoring, the new method is named 'f', resulting in changes in code behavior, that is, before refactoring, the method() in class C is called f() in class C, and after refactoring, the method() in class B is called f() in class B. Before refactoring, the code is as follows:
The resulting code after refactoring is as follows:
The text was updated successfully, but these errors were encountered:
- modify ExtractMethodRefactoring to test if the new method name
collides with an existing method name being used by a class that
sub-classes the one creating the new method
- add new test to ExtractMethodtests
- fixeseclipse-jdt#1516
When the 21-line statement in class B is selected to perform extraction method refactoring, the new method is named 'f', resulting in changes in code behavior, that is, before refactoring, the method() in class C is called f() in class C, and after refactoring, the method() in class B is called f() in class B. Before refactoring, the code is as follows:
The resulting code after refactoring is as follows:
The text was updated successfully, but these errors were encountered: