-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppress resolution if 'Configure problem severity' is the only available options #1614
Comments
Quick fix
for 'No fixes available' ones
The QuickFix menu is provided by platform, not by PDE. Beside that the main problem is that computing Quickfixes can be an expensive task so disable the menu item might not be possible without performance issues when opening the menu. |
Upon right click on the problem to get the context menu pop-up, the code passes through this function in PDE (before the context menu pop-up is showed) Lines 159 to 165 in 975f72b
via function hasResolution Lines 257 to 259 in 975f72b
And in cases where it reaches to Line 164, where marker id is getting set with PDEMarkerFactory.NO_RESOLUTION, the |
Then the title of the issue is misleading. PDE itself can't disable the menu, but it should report proper |
Quick fix
for 'No fixes available' ones
Yes, I agree. The underlying problem is that there are several markers where the problemID has the value PDEMarkerFactory.M_ONLY_CONFIG_SEV as the resolution, i.e., the "Configure problem severity" option only. Line 55 in 975f72b
Lines 146 to 151 in 975f72b
To avoid misleading the user, one solution could be to return PDEMarkerFactory.NO_RESOLUTION for all such cases where the marker problemID only has PDEMarkerFactory.M_ONLY_CONFIG_SEV as the resolution. In the future, we could implement an option to show 'Configure problem severity' along with the correct quick fix implementation. |
Currently, the context menu option "Quick fix" is visible for problems where no fix is available, which then leads to a pop-up menu saying No fixes available.
There are many such issues for this condition. Attaching a sample here for the issue - a space added after the header name before the ':'.
Steps to reproduce:
This behaviour misleads developers into thinking that a quick fix is available for the problem. After clicking the 'Quick fix' context menu option, it states 'No fixes available,' which can waste developers' time and cause frustration.
To avoid this misleading, one solution could be to disable the context menu option 'Quick fix' where no fixes are available like this:
The text was updated successfully, but these errors were encountered: