-
-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move snippets to separate repo? #31
Comments
@sebmck Thoughts? Makes sense to me. I actually want to get rid of the snippets all together. The only snippet I use is for |
I'm going to vote in favour of moving snippets out. I have preference on something like |
Oh yeah, that is what Gulp does. Although it sounds like a cop out, showing users how to get down-and-dirty with snippets means that they can tweak them to their own style. I'd like another 👍 from another collaborator 😄 |
@zertosh I don't use snippets at all so I don't really have an opinion. Happy to create a new repo if necessary 😜 |
Fixed by #43 |
Thanks :D!! |
Noooo I was just getting used to the snippets! :) Creating them manually with the given instructions is a pain, so I placed them in a repo again. |
@0x80 What I really wanted to do was have Sublime ignore the snippets, but AFIK there is no way for a package to selectively self-ignore a directory. But, there are two alternatives: I could ZIP up the snippets, or change their extension to something like |
IMHO is a good idea to keep them in a separate repo, maybe available on package control :-) |
A zip would work for me, but maybe a repository makes sense. I would choose a zip over file renaming. |
What would a dedicated babel snippets package look like? Just React stuff seems a little odd. |
@sebmck can I haz a |
@sebmck thanks! |
FWIW, sublime-react already provides the original snippets in a separate repo and works in combination with Babel. |
Not a fan of having snippets automatically included :(. Could we move em to a separate repo?
I have my own set of personal JS snippets, and since you can't disable package-specific snippets my only choice would be to fork 6to5-sublime and keep it up-to-date manually everywhere I have a sublime text installation.
The text was updated successfully, but these errors were encountered: