-
Notifications
You must be signed in to change notification settings - Fork 28k
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
Allow triggering quick fixes from problems view #52627
Comments
Following are the quick fixes when shown in problems view. Let me know if it is ok @jrieken FYI |
I like it. This is per error/warning, right? Per file we could offer source actions, like orga-imports et al. |
Yeah it is per marker. Sure, we can offer source actions and may be also fix all action on file. |
@sandy081 do I see if quick fixes are available without opening the context menu? |
@kieferrm No, you don't. Otherwise, we can show overlaid light bulb icon on top of error/warning icon? |
@sandy081 that's something we should experiment with. |
Maybe on select/hover? |
On select might inline with editor |
I think Source Actions are not a good fit as they are nothing to do with diagnostics. |
A light bulb will be shown if there are quick fixes available for a problem. For performance reasons, quick fixes check is done by
So, it is necessary that the extension should provide the diagnostics in the quick fixes. See CodeAction.diagnostics Otherwise, light bulb indicator is not shown, but the quick fixes are shown in the context menu. I will file an issue against those extension which are not providing diagnostics in quick fixes so that the light bulb can be shown for their diagnostics in Problems view. |
Feature request
Provide a way to trigger a quick fix from the problems view.
For example, for the javascript:
A quick fix is available:
But this is not shown or indicated in the problems view:
Additionally, when you click on the problems entry, the editor is not focused so you cannot use a keyboard shortcut to trigger the quick fix
The text was updated successfully, but these errors were encountered: