-
Notifications
You must be signed in to change notification settings - Fork 19
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
Grunt and Lint #8
Conversation
There are still a number of linting violations, however, I was unsure how you wanted to handle them (or how the automated build should handle them ;))
|
Looks great! I had to install Running
Am I missing something? That's on Windows, will test on OS X later. That's the first time I use pull requests, is it possible to separate the grunt addition and lint corrections into two separate commits? |
Sorry, sometimes I have remind myself I'm talking outside my dev department. Forgive me.
I'm exclusively on OSX and Linux. |
@Farof I can finish the rest of the protocols today. Can you verify a few findings (I believe the following are true, just need a second set of eyes). EVERY protocol from (and including) "tracker_eventid_typeid" and below is EXACTLY the same in the .py repository for EACH PROTOCOL. The only TRUE differences between each file is the enum arrays have different structures (and we want to export a version number). |
I've been reworking |
I think this is all I want to do with this commit. All protocols with the exception of protocol29406 are complete and linted, 1 errors. The only exception is:
Not sure how you wanted to handle that, we can merge it, then fix it. |
Merging the doc and then looking at this. |
I'm looking at grunt, if you know how to remove the protocols addition from this pull request and put them in another dedicated one I would appreciate it and would love to have a quick rundown on how to do that. |
You would like two PRs? 1 for Grunt/Lint, 1 for Protocols? |
Yes, I could merge the protocols right away and get grunt working separately. Thank you. |
Grunt is just a devDependency. That's all I added there. It's just a tool to help develop, never gets to the NPM package. |
Honestly, it's a pain in the split at this point because there have been so many merges in from master. grunt is 1 file ( |
Merged the protocols separately. Grunt gives me an "out of memory" error on OS X as well. See #16. |
Added Gruntfile.js for automatic development.
Linted a few files that showed up as violations.
(If you are not familiar with Grunt, it is a development tool to constantly lint/build/run your application while you are editing code. Currently, the default task does nothing, however
grunt lint
will continuously lint your files while editing them to make sure you did not miss a comma or other silliness.npm install
to install all devDependencies).