Bug 474103 - [quick assist] invocation via menu item "Quick Fix" is confusing
Summary: [quick assist] invocation via menu item "Quick Fix" is confusing
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-02 17:16 EDT by Stephan Herrmann CLA
Modified: 2023-01-25 13:30 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2015-08-02 17:16:57 EDT
It seems people don't expect "quick assists" when they see the menu item called "Quick Fix". [1]

- Should the menu item name be context sensitive according to presence / absence of a fixable problem at the cursor location?

Assuming that only one kind of assists will be offered at a time, there shouldn't be a conflict in naming the menu item.

[1] http://stackoverflow.com/a/30662364/4611488 see first comment.
Comment 1 Dani Megert CLA 2015-08-03 05:06:24 EDT
It could also confuse people if we rename it after so many years. If we start to look into this we also have to go over our documentation, which is not consistent regarding this.
Comment 2 Eclipse Genie CLA 2020-06-26 15:27:19 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 2023-01-25 13:30:01 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.