Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow `source.fixAll` code action
See original GitHub issueThere’s a code action called source.fixAll, referenced here, that’s missing from the CodeActionKind enum.
Happy to add it via PR if welcome.
Issue Analytics
- State:
- Created 10 months ago
- Comments:7
Top Results From Across the Web
Code actions on Save can't be configured correctly #84602
What I try to do is the following: if source.fixAll is set to true provide eslint auto fix options. allow users to disable...
Read more >VSCode - editor.codeActionsOnSave - source.fixAll.eslint ...
I want VS Code to fix all linting errors on save, but ignore warnings. This rule fixes everything it can on save: "editor....
Read more >Format Code Action - Visual Studio Marketplace
Disable formatOnSave and use the source.formatDocument codeAction ... fixAll.format as the codeAction, that still works for legacy purposes.
Read more >How to get ESlint and Prettier to play nice in VS Code?
Using this and the editor.codeActionsOnSave setting in VS Code you can specify the order in which to run the eslint codeAction, source.fixAll.
Read more >Python in Visual Studio Code – August 2022 Release
Pylance now offers a code action for removing all unused imports when ... also configure VS Code to run all available “fix all”...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great, #294 is waiting for review from the team, so will probably be released in the next few hours. Then you’ll be able to use either; the current release or the alpha release 😏
Haha, well I’m sure that’ll be the first of many star struck moments. I think Ruff is an awesome project.
I’ll get #294 released then.
To the best of our current knowledge, that
1.0.0branch is in fact ready for release. It’s really just down to me to decide when the right moment is to release it. I’m relatively new to the project, so a bit nervous to force a breaking change onto the world. I’m basically just waiting to see if there’s any more feedback. So, if you’re in the middle of developing a Pygls-server I would actually recommend1.0.0a2over the current stable release, just because it’ll save you the refactor later on.Actually, now that I think about it, I should update the README to say that we no longer recommend starting new projects with the current
v0.x.