feat(snippet): add `mini.snippets` #1313

5 / 5 tasks completed

All tasks have been completed

Task	Status
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`	Incomplete
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`	Incomplete
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	Completed
`README` is properly formatted and uses fenced in links with `<url>` unless they are inside a `[title](url)`	Completed
Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).	Completed
Proper usage of `opts` table rather than setting things up with the `config` function.	Completed
Proper usage of `specs` table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).	Completed
Add a line to `print(global.test or "NOT FOUND")` here where you calculate the resolution of the config which is used throughout `mini.snippets`: https://github.com/echasnovski/mini.nvim/blob/890db26e37bb28d8a95f05570dd0d9fa757b698b/lua/mini/snippets.lua#L1558	Incomplete
Start the editor and use `mini.snippets`. Notice that it keeps printing `NOT FOUND`, but if you run `:lua =_G.MiniSnippets.config.test` you will get `FOUND`	Incomplete