feat(trouble-nvim): integrate snacks.nvim picker
📑 Description
Allow the integration of snacks.nvim with trouble.nvim
Review Checklist
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
-
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex.
feat(utility): added noice.nvim plugin -
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex.
fix(noice-nvim): fix LSP handler error -
[x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
-
[x]
READMEis properly formatted and uses fenced in links with<url>unless they are inside a[title](url) -
[x] Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).
-
[x] Proper usage of
optstable rather than setting things up with theconfigfunction. -
[x] Proper usage of
specstable for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).
I don't think anyone can review this because it's not clear what it does.
It allows the snacks picker to send the entries to trouble.nvim
Just like how with telescope you can send the items to quick-fix list or location list. This code allows you to send the items found by snacks pickers to the trouble.nvim list with all the added benefits of trouble.nvim
im taking a look at this sometime in the next 24h