Bug 532441 - [quick fix] Quick fix > Change method won't adapt uses of that method
Summary: [quick fix] Quick fix > Change method won't adapt uses of that method
Status: CLOSED DUPLICATE of bug 160212
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-14 07:55 EDT by Marko Zajc CLA
Modified: 2018-05-07 12:06 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Zajc CLA 2018-03-14 07:55:56 EDT
Changing a method (eg adding a parameter) via Quick fix will not actually refactor it like Refactor > Change method signature and thus resulting in cases where a parameter was added to satisfy one call but not the others that don't implement those changes (eg a new parameter). So, take this code for example:

	public static void main(String args[]) {
		doStuff("Play", 25);                
		doStuff("Playf");                   
	}                                       
                                            
	static void doStuff(String s) {         
		System.out.println(s);              
	}

The first call will show an error and will have a quick fix named "Change method 'doStuff(String)': add parameter 'int'". Upon applying it, the first call will be satisfied but the latter will now have an error with the opposite quick fix (removing the parameter) so the only sure way to actually apply such quick-fixes is to manually go to that method and refactor it with "Change method signature".
So, could there be at least a setting to open the "Change method signature" window on such changes?
Comment 1 Dani Megert CLA 2018-05-07 12:06:05 EDT

*** This bug has been marked as a duplicate of bug 160212 ***