Bug 96932

Summary: [quick fix] No "create field" quick fix inside enum
Product: [Eclipse Project] JDT Reporter: David Saff <david>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description David Saff CLA 2005-05-27 04:53:31 EDT
In I20050527-0010

Given code:

public enum TheEnum {
	ONE, TWO;
	
	private int foo() {
		return fCount;
	}
}

A quick fix on fCount does not offer "Create field 'fCount'", but it should
Comment 1 Dirk Baeumer CLA 2005-05-27 05:05:03 EDT
Not ciritical for 3.1 since fields aren't common in enums.
Comment 2 David Saff CLA 2005-05-27 05:10:43 EDT
I don't have a good grasp on what's common, so take this with a grain of salt,
but there's a field in the second enum example ever published:

http://www.jcp.org/aboutJava/communityprocess/jsr/tiger/enum.html
Comment 3 Eclipse Genie CLA 2020-09-02 11:52:27 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.
Comment 4 Eclipse Genie CLA 2022-12-14 13:29:25 EST
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.