refex
actions-preview.nvim
refex | actions-preview.nvim | |
---|---|---|
3 | 4 | |
14 | 296 | |
- | - | |
5.0 | 7.1 | |
7 months ago | about 2 months ago | |
Python | Lua | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
refex
-
Writing and Linting Python at Scale
As someone who worked on a similar tool (https://github.com/ssbr/refex/tree/main/refex/fix/fixers, I did a bunch of the work to prep this for open-sourcing, though I think all my contributions are hidden behind the "Google-internal" anonymization), having auto-applied or auto-appliable fixers like this is super useful.
They can be auto-applied by post-commit (e.g. a generic `git fixcommit` style command that runs all the relevant lint tools and fixes them in the working copy, letting you review before push), or applied during code review (automatic comments with a "click here to apply fix" interface), both of which are nice.
Plus the same underlying tooling can be used to write more complex one-off fixes that may be used for migrations or cleanups.
-
I learnt to use ASTs to patch 100,000s lines of python code
You might like Refex, which automates AST transformations like this:
-
Semgrep: Like Grep but for Code
There's lots of confusion about what semgrep does here, which is kind of unfortunate. I haven't touched it much, but I have built a very similar tool (I'm one of the contributors to refex[1], which is a very similar project).
The starting point of semantic grep is very useful. When you have a big codebase, you often want to detect antipatterns, or not even antipatterns, but just uses of a thing, say you're renaming a method and want to track down the callers.
Being able to act on the AST, instead of hoping you searched up all of the variants of whitespace and line breaks and, depending on the specific example, different uses of argument passing, is really useful.
But often when you're semantically grepping, your goal is to replace something with something else (this is what refex was initially built for: to aide in large scale changes in python, as a sort of equivalent to the C++ tools that Google uses).
But then you want to shift left even further: once you have a pattern that you want to replace once, you can just enforce that a linter yell at you when anyone does it again. So it's very natural to develop a linter-style thing on top of one of these[2].
This is, as I understand it sort of the same thing that happens in C++: clang-tidy and clang-format are written on top of AST libraries that can be used for ad-hoc analysis and transformations, but you can also just plug them into a linter.
The thing is, for most organizations, enforcing code style and best practices is more valuable than apply a refactoring to 10M lines of code, because most organizations don't have 10M lines of code to refactor. That doesn't mean that these tools aren't also useful for ad-hoc transforms and exploratory analysis. They absolutely are!
[1]: https://github.com/ssbr/refex
[2]: https://github.com/ssbr/refex/tree/main/refex/fix
actions-preview.nvim
-
Code action previews with `fzf-lua`!
Ty for the kind words everyone and shoutout to the author of actions-preview.nvim for the diff generation code I reused.
-
Writing and Linting Python at Scale
Adding to what other commenters said, ESLint also works like this.
However in an IDE setting it's not exactly "auto"; you have to click the light bulb and accept the fix (idk about VSCode, but in Neovim you can even get a preview of the diff [1]). This is what I'm working on a Fixit PR for right now.
[1] https://github.com/aznhe21/actions-preview.nvim
- How to use telescope to show code actions and codelens instead of noice?
-
Question about Rust code actions
I'm not sure about how actions-preview.nvim works, but are you sure you set it up correctly?
What are some alternatives?
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
telescope-ui-select.nvim
checkr - Custom static analysis rules for the lazy. Write project specific static analysis checks in a few lines of code.
nvim-lspconfig - Quickstart configs for Nvim LSP
tree-sitter-swift - Swift grammar for tree-sitter
telescope-manix - A telescope.nvim extension for Manix - A fast documentation searcher for Nix
ocaml-tree-sitter-semgrep - Generate parsers from tree-sitter grammars extended to support Semgrep patterns
telescope-color-names.nvim - Neovim plugin and Telescope extension for picking X11 / web color names
CCGrep - Code Clone Detector like grep
tldr.nvim - 🔠A Telescope previewer for tldr-pages
Bear - Bear is a tool that generates a compilation database for clang tooling.
telescope-insert-path.nvim - Insert file path on the current buffer using Telescope.nvim