Bug 401262 - [refactoring] [rename] [extract local] If possible, report name conflicts before starting preview
Summary: [refactoring] [rename] [extract local] If possible, report name conflicts bef...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 23:59 EST by Mohsen Vakilian CLA
Modified: 2013-02-20 06:03 EST (History)
2 users (show)

See Also:

Attachments
This screenshot of the Rename Package refactoring shows how this automated refactoring warns the user about a name conflict immediately the first input page. (32.64 KB, image/png)
2013-02-19 23:59 EST, Mohsen Vakilian CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mohsen Vakilian CLA 2013-02-19 23:59:34 EST 
Created attachment 227311 [details]
This screenshot of the Rename Package refactoring shows how this automated refactoring warns the user about a name conflict immediately the first input page.

Eclipse refactorings are good at warning the user about unconventional names immediately. The refactoring tool should warn users about conflicting names immediately as they type the names on the refactoring wizard input page.

Rename Package warns the user about conflicting names on the first input page, but, other refactorings like Extract Local Variable, Rename Local Variable, Package, Compilation Unit, Type, Method and Field report the conflicting name on a separate page after the user indicates that he/she is willing to apply the refactoring. This causes additional overhead, because the user has to navigate back to the first page of the wizard to change the name.

14 of the participants of the CodingSpectator study <http://codingspectator.cs.illinois.edu/> got error messages related to name conflicts from Eclipse in a total of 43 refactoring invocations. The participants proceeded with the refactoring in 20 cases and canceled it in the remaining 23 cases.