-
Notifications
You must be signed in to change notification settings - Fork 4
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
Added a Sass version with build test using Gulp #4
Conversation
Oh, and also, since I'm using a I already bumped both |
@emileber This looks great, sorry it took a while for me to get back to this. The existing API is untouched which is great, and if it can be used immediately with npm, that sounds like an immediate win. I hear bower is "less cool" now anyway 😉 Great idea with the custom prefix BTW 👍 Travis is a nice direction, unless this project gets super big I don't feel the need for it quite yet. I assume this is tested through and it works? |
(I will double check on my side before merging) |
I personally use both npm and bower. npm is usefull for everything, but I like splitting my backend dependencies and my frontend dependencies using the right tool for each, bower being best for frontend lib. The best is to avoid imposing choices to users by providing both. You're right, Travis might be overkill for a small project like this one, but it's free for open-source project and it's easy to activate, just toggling a checkbox. This is tested, I'm using my own fork in an big enterprise app which uses Sass until this is merged. |
Any update on this ? |
@jimmykane James looks busy, so if you really need the sass version, you can use the branch
|
@emileber busy is definitely what I am, however I've been disregarding my duties as a maintainer, and disrespecting you and your contribution by not merging it for a long time. I'm happy to push the button now --- is there anything I need to do? |
Also, it would be useful to push another version to NPM and tag it in the repo as well. |
@emileber Thank you for your contribution, and sorry for ignoring you for so long. It's now on npm! 🎉 |
You're the real MVP, thanks for the open source font plugin ❤️ |
@jamesadevine @emileber Thanks a ton guys. I can now implement these activity icons on my project. You are both the best! 😘 |
This closes #3.
I applied the change I proposed in #2 only to the
.scss
file, concerning a clash with other font libs usingicon-
as a default prefix.I added default variables inspired by simple-line-icon to enable changing:
I also added a precommit hook which prevent committing a
.scss
file that can't be built (at least).There's a
.travis.yml
file which could serve the same test server-side to ensure each commit and pull request meets the requirements.More could be added to this, like a task to build the fonts from the
src
folder, etc.