Bugzilla – Full Text Bug Listing
| Summary: | [5.0][content assist] Content Assist for annotation elements should add a '=' | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, vkhomyackov |
| Version: | 3.1 | Keywords: | bugday, helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 89602 | ||
| Bug Blocks: | |||
time permitting for M7 Setting to remind until dependent bug has been fixed. reopening We don't get any proposals for an empty prefix, currently (consistent with code assist behavior in other situations). However, '=' should be included in the trigger chars for the annotation element reference, which would be an easy fix. Low priority for 3.1. not for 3.1 Bump. Still present in 3.7 - will anybody finally fix it? In my everyday work after most of annotation properties I should manually type ="" (equal sign and double quotes for string value). (In reply to comment #6) > Bump. Still present in 3.7 - will anybody finally fix it? In my everyday work > after most of annotation properties I should manually type ="" (equal sign > and double quotes for string value). We won't work on this bug but accept a high quality patch. |
I20050330-0500 public class Try { @Tag(/*ContentAssist*/) void n() {} } @interface Tag { String name() default "name"; String value(); } - execute content assist where indicated above -> expected: proposal 'value' inserts 'value=' -> was: inserts just 'value' BTW: content assist after 'value=' does currently not work (bug 89602).