-
Notifications
You must be signed in to change notification settings - Fork 73
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
CSS Namespacing #49
CSS Namespacing #49
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the .gitignore change, things looks great!
@@ -23,6 +23,6 @@ build/Release | |||
# Deployed apps should consider commenting this line out: | |||
# see https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git | |||
node_modules | |||
dist |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The compiled code shouldn't be committed to Github. I compile when creating a new release and push that to NPM. I think compiled code in Github is a bit icky as it creates weird diffs plus is hard to remember to keep updated plus isn't that useful anyways since you only need the compiled version when installing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@KyleAMathews I agree; that was leftover from the original PR. I didn't alter it on the off chance that I was missing something but since you've confirmed the compiled code shouldn't be there, I'll update the PR.
Published a 2.0! Thanks @kkozee and @carlos-stored! |
@KyleAMathews