You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rafamadriz/friendly-snippets currently attributes framework specific snippets to framework filetype so for example angulars snippets are all bundled into an angular filetype. I am working on a pr to divide them up as seeing both html and ts snippets in each of those filetypes is significant noise especially if you enable multiple frameworks. The issue however is if they are bound to html and ts filetypes that disables their opt in character. That poses the question, aside from dividing this up into multiple repos is there any way to make the framework snippets opt in while preserving the filetypes of each snippet subset?
Right now my proposed solution is to just make a filetype like angular-html and make the user enable it for each ft but that makes the user write ~4 lines of configuration for each framework to enable it and that's pretty verbose despite the better scoping of snippets.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
rafamadriz/friendly-snippets
currently attributes framework specific snippets toframework
filetype so for example angulars snippets are all bundled into an angular filetype. I am working on a pr to divide them up as seeing both html and ts snippets in each of those filetypes is significant noise especially if you enable multiple frameworks. The issue however is if they are bound to html and ts filetypes that disables their opt in character. That poses the question, aside from dividing this up into multiple repos is there any way to make the framework snippets opt in while preserving the filetypes of each snippet subset?Right now my proposed solution is to just make a filetype like angular-html and make the user enable it for each ft but that makes the user write ~4 lines of configuration for each framework to enable it and that's pretty verbose despite the better scoping of snippets.
Beta Was this translation helpful? Give feedback.
All reactions