Question 1

How to set up tiny-code-action.nvim with Telescope?

Accepted Answer

Install the plugin with Lazy.nvim, add telescope.nvim as a dependency, and set picker = 'telescope' in opts. Then, map a key to require('tiny-code-action').code_action() as shown in the README installation section.

Question 2

tiny-code-action.nvim vs built-in Neovim LSP code actions?

Accepted Answer

This plugin adds visual diff previews, multiple picker choices, and advanced filtering, whereas built-in actions lack previews and customization. It's better for safely reviewing changes but adds more dependencies and configuration.

Question 3

Why is my code action preview slow in tiny-code-action.nvim?

Accepted Answer

If using the delta backend, it can be slow for large actions. Switch to the vim backend for better performance, as recommended in the README warning, or reduce header_lines_to_remove in backend_opts.

Question 4

How to customize icons for code actions in tiny-code-action.nvim?

Accepted Answer

Use the signs option in setup to assign icons per action kind, like setting refactor = {'', {link = 'DiagnosticInfo'}}. You can add custom kinds or remove NerdFonts icons by adjusting this table.

Question 5

How to filter code actions by kind in tiny-code-action.nvim?

Accepted Answer

Use the filters option or context.only, such as setting context = { only = 'refactor' } in the code_action call. This filters actions hierarchically, so 'refactor' includes subkinds like 'refactor.extract'.

Question 6

Does tiny-code-action.nvim work with Omnisharp?

Accepted Answer

Yes, it fully supports language servers with partial code actions like Omnisharp, as highlighted in the key features. Ensure your LSP is configured properly, and use the plugin's picker to view and apply actions.

tiny-code-action.nvim

What is tiny-code-action.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions