Bug 430039

Summary:	[1.8][actions] Open Declaration (F3), Quick Hierarchy (Ctrl+T) etc. on lambda expression
Product:	[Eclipse Project] JDT	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, manju656, noopur_gupta
Version:	4.4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	429814, 429785
Bug Blocks:

Description Markus Keller

2014-03-10 15:13:02 EDT

After bug 429814 is fixed, we should work out what Open Declaration (F3) is supposed to be doing on a lambda expression's "->".

The easy answer is it should jump to the declaration, i.e. to itself (like F3 on a method declaration just selects the method name).

However, that's rarely useful/wanted, and there's a much more useful target:
The implemented functional interface method. I.e. "Open Super Implementation".

This is what happens right now (with bug 429814) on Ctrl+Click. It currently doesn't work on F3 because of bug 429785 (codeSelect doesn't work without selection) and because SelectionConverter#codeResolve(IJavaElement, ITextSelection) now always invokes codeSelect at the *end* of the selection (since bug 75353).

The SelectionConverter#codeResolve methods should at least handle a selection of "->" (length == 2) properly and invoke codeSelect on the given selection. Selections of length 0 should work as expected after bug 429785 is fixed.

Comment 1 Noopur Gupta

2016-04-23 03:30:14 EDT

Moving to 4.7 as bug 429814 is still open.

Comment 2 Noopur Gupta

2017-05-10 05:41:30 EDT

Moving to 4.8 as bug 429814 is still open.

Comment 3 Noopur Gupta

2018-04-13 06:26:35 EDT

Removing the target milestone.

Comment 4 Eclipse Genie

2020-09-20 02:51:32 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 5 Eclipse Genie

2022-11-30 11:05:45 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.