Closed EmilyGraceSeville7cf closed 1 year ago
the snip should be placed at server side? or just for vsc?
It's better to place them at server side like in Bash IDE for VS Code, but I don't know how to do it now, not TypeScript developer. I don't like the idea to have several extensions just to provide both code hints and snippets. I prefer to have one good extension which provides these features. 😄 BTW, there is another similar extension with snippets provided too.
yes, i think if this snip fs placed at client for vsc only, then looks unnecessary, or conflict. // i recall vsc had general way to add snips.
if you like to add snip within lsp server package, i thought better be in server folder.
I prefer to have one good extension which provides these features.
i do not use vsc much, but to vim, there several plugins can generally offer snips for many langs, and can do without lsp.
but you're ok to add snips into lsp server package, (which should be in server folder), that would be workable for all clients (not only vsc or vim), that's a good impl as well.
The snippets ended up on server side. Hopefully this makes more sense and lets all editors to benefit from them.
but I don't know how to do it now, not TypeScript developer.
@Beaglefoot would you mind help @EmilySeville7cfg move this snip file to right place?
but I don't know how to do it now, not TypeScript developer.
@Beaglefoot would you mind help @EmilySeville7cfg move this snip file to right place?
It's already there. The last published version provides snippets on server side.
thx, i just verified a bit, but seems not work still. maybe should directly registered snippets.json to src/snippets.ts as const var?
Hate to say it but works on my side:
Would you mind to open an issue describing all the steps to replicate?
// i opened #44
seems a bit complex to me to desc the steps, i am not using vsc. but i am trying to debug a bit, please check #44
the snip should be placed at server side? or just for vsc? if for vsc only, then perhaps there are some local snip plugin/extension can do that already.