Bug 481258 - Content assist does not provide value element related proposals if annotation as more than one element
Summary: Content assist does not provide value element related proposals if annotation...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-02 12:28 EST by Sebastien Arod CLA
Modified: 2022-06-23 15:46 EDT (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 Sebastien Arod CLA 2015-11-02 12:28:39 EST 
Given the following annotation:
public @interface MyAnnotation {

	enum MyEnum { 
		VALUE1, VALUE2
	}
	MyEnum value();	
	
	String additionalElement();
	
}

The content assist should list the proposals for "value" element, i.e. the enum list, when triggering completion after typing "@MyAnnotation(".

Currently it only provide the elements list ("value", "additionalElement") as proposals.

Note that this works fine if annotation as only the "value" element.
Comment 1 Eclipse Genie CLA 2020-06-10 15:33:50 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 2 Eclipse Genie CLA 2022-06-23 15:46:34 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.