Skip to content
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

Closed
cesarandreu opened this issue Feb 13, 2015 · 15 comments
Closed

Move snippets to separate repo? #31

cesarandreu opened this issue Feb 13, 2015 · 15 comments
Labels

Comments

@cesarandreu
Copy link

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.

@zertosh
Copy link
Member

zertosh commented Feb 13, 2015

@sebmck Thoughts? Makes sense to me. I actually want to get rid of the snippets all together. The only snippet I use is for for-loops lol - I don't know if people actually use them. A wiki section (or a README-snippets.md on "Roll your own snippets" with samples could a good compromise.

@dashed
Copy link

dashed commented Feb 13, 2015

I'm going to vote in favour of moving snippets out.

I have preference on something like snippets.md, which explains how to copy-paste snippets, and also where folks can PR against to add snippets for various 6to5 features (not just JSX). Something like what gulp does.

@zertosh
Copy link
Member

zertosh commented Feb 14, 2015

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 😄

@sebmck
Copy link

sebmck commented Feb 14, 2015

@zertosh I don't use snippets at all so I don't really have an opinion. Happy to create a new repo if necessary 😜

@zertosh zertosh added the todo label Feb 15, 2015
@zertosh
Copy link
Member

zertosh commented Feb 19, 2015

Fixed by #43

@zertosh zertosh closed this as completed Feb 19, 2015
@cesarandreu
Copy link
Author

Thanks :D!!

@0x80
Copy link

0x80 commented Feb 28, 2015

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.

@zertosh
Copy link
Member

zertosh commented Feb 28, 2015

@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 whatever.sublime-snippet.disabled. Both would require some work on part of the user - but less so than copy/pasting. Do you think any of those options works for you?

@gpbl
Copy link
Contributor

gpbl commented Feb 28, 2015

IMHO is a good idea to keep them in a separate repo, maybe available on package control :-)

@0x80
Copy link

0x80 commented Feb 28, 2015

A zip would work for me, but maybe a repository makes sense. I would choose a zip over file renaming.

@zertosh
Copy link
Member

zertosh commented Mar 1, 2015

What would a dedicated babel snippets package look like? Just React stuff seems a little odd.

@zertosh
Copy link
Member

zertosh commented Apr 15, 2015

@sebmck can I haz a babel-snippets (or babel-sublime-snippets) repo?

@sebmck
Copy link

sebmck commented Apr 15, 2015

@zertosh
Copy link
Member

zertosh commented Apr 15, 2015

@sebmck thanks!

@jgebhardt
Copy link

FWIW, sublime-react already provides the original snippets in a separate repo and works in combination with Babel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants