Bug 67974 - [rename] Rename constant/field/variable/parameter/method/type should provide code assist in the rename dialog
Summary: [rename] Rename constant/field/variable/parameter/method/type should provide ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 80371 (view as bug list)
Depends on: 38111
Blocks:
  Show dependency tree
 
Reported: 2004-06-21 05:55 EDT by Erich Gamma CLA
Modified: 2019-05-08 09:25 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erich Gamma CLA 2004-06-21 05:55:21 EDT
Bug# 67930 indicates that users are expecting code assist in the rename field 
dialog.

We should offer code assist in the dialog and suggest the same proposals you 
would get when entering the field in the editor and pressing ctrl+space.
Comment 1 Dirk Baeumer CLA 2004-06-21 06:06:53 EDT
Fair request.
Comment 2 Markus Keller CLA 2006-06-16 05:05:54 EDT
*** Bug 80371 has been marked as a duplicate of this bug. ***
Comment 3 Markus Keller CLA 2006-06-16 05:10:29 EDT
The name should be based on
- the original name (depends on bug 38111) for renaming types
- the original name and the type of the element for renaming constant/field/variable/parameter/method
Comment 4 Martin Aeschlimann CLA 2008-05-02 10:31:39 EDT
Not for 3.4
Comment 5 Eclipse Genie CLA 2019-05-07 15:57:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.