-
Notifications
You must be signed in to change notification settings - Fork 104
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
Project Structure #82
Comments
What about introducing a style guide? Perhaps adding jscs to gulp and using Airbnb's Style Guide |
we have JShint running as a pre-processor on our test suite |
Wellll, we have tags now :) |
@dperrymorrow, I was thinking more along the lines of conformity with such things as quotation style, white-space, named functions etc.. something JSHint isn't designed for. |
See issue #37 @LeaVerou is pretty opposed to very opinionated linters. |
There have been a lot of conversation so far relating to the project structure, so I'm going to summarize them all here.
We have the following criteria we'd like to solve:
We also don't want the project to be more work than it already is. So let's take a look at this post-commit hook by Domenic: https://gist.github.com/domenic/ec8b0fc8ab45f39403dd.
I'd like to get SauceLabs or Browserstack set up as well. We can get a free account since this is open source.
Last, we want to consider the possibility of being able to execute the karma tests in-browser, as part of the
gh-pages
branch. Currently, I only know of QUnit doing this well. Haven't really seen solutions for Karma.The text was updated successfully, but these errors were encountered: