Bug 303419 - Need some out-of-the-box thinking for renaming types
Summary: Need some out-of-the-box thinking for renaming types
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: IDE4EDU (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 23:13 EST by Wayne Beaton CLA
Modified: 2014-01-09 15:38 EST (History)
0 users

See Also:

Attachments
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 Wayne Beaton CLA 2010-02-20 23:13:09 EST 
Copied from Bug 299459 Comment 4

How about we try something more radical? If the user changes the name of the class in the editor, can we just automatically rename the file?

I know that if you do this, JDT will report an error that you can fix using a Quick Fix. That means that all the code is there. Can we tap into it and just make it happen automagically? Can we do it without forking JDT code?

I'm thinking that we can listen in on the same events that the problems view uses to determine what problems to display. If we find a problem that has to do with a name mismatch, we just automatically invoke whatever quick fix solves that problem.