garymjr / nvim-snippets

Snippet support using native neovim snippets
MIT License
215 stars 13 forks source link

Bug: custom snippet #5

Closed rubiin closed 3 months ago

rubiin commented 3 months ago

When using custom snippet with nested folders, the plugin does not work. I think this has to do with https://github.com/garymjr/nvim-snippets#todo (Undecided) Add support for friendly-snippets package.json definitions

chrisgrieser commented 3 months ago

I second this. The package.json is used by VS Code (and by Luasnip and friendly snippets) to determine which filetype matches which file(s), basically what the extended_filetypes config option does.

Implementing this would also save the plugin from requiring an option for friendly-snippets, as the path to the repo could simply be added to search_paths. Basically, the package.json is part of the VSCode snippet format standard, and it would be preferable to implement that standard.

edit: the workaround I now used is to de-nest my whole snippet directory, putting everything into the snippet root, and also adding all the stuff I have already added in package.json manually to extended_filetypes

rubiin commented 3 months ago

@chrisgrieser shoutout to you . Been using some of your plugins and also taking some stuffs from your neovim configs. Great stuff

garymjr commented 3 months ago

Adding support for reading package.json is something I plan to add. I'll spend some time this week (or weekend if I can't find time) and get this added.

Geobert commented 2 months ago

Hi,

I’m using LazyVim and it ships with nvim-snippets. My custom snippets are https://codeberg.org/geobert/nvim-config/src/branch/main/snippets but I can’t make them work :-/ They don’t show up in markdown files

EDIT: I’m using nvim 0.10 of course EDIT2: I thought that "snippets" source was setup by LazyVim but I must have overwritten it as adding it manually make it work :)