Bug 486445 - [content assist] Substring completion for Javadoc tags
Summary: [content assist] Substring completion for Javadoc tags
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-25 04:19 EST by Noopur Gupta CLA
Modified: 2022-10-05 18:03 EDT (History)
4 users (show)

See Also:


Attachments
patch (1.26 KB, patch)
2016-01-25 04:19 EST, Noopur Gupta CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Noopur Gupta CLA 2016-01-25 04:19:27 EST
Created attachment 259358 [details]
patch

public class C {
	/**
	 * @p
	 */
	public static void main(String[] args) {}
}

In the above example, invoke content assist after "@p" when substring completion is enabled in preferences. => ICodeAssist#codeComplete does not return substring proposals like '@deprecated'.

Fix should go in CompletionJavadocParser#possibleTags, which should have a check for substringMatch along with prefixEquals. See attached patch.

However, before calling #substringMatch, there should be a check to see if substring completion is enabled. I am not sure how this information can be accessed in CompletionJavadocParser from CompletionEngine#options.

Also, the proposals relevance should be adjusted similar to bug 481752.

Jay, please have a look.
Comment 1 Manoj N Palat CLA 2018-05-16 01:38:12 EDT
Bulk move out of 4.8
Comment 2 Eclipse Genie CLA 2020-07-08 14:58:38 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 3 Eclipse Genie CLA 2022-10-05 18:03:03 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.