Looked for trouble spots with JSHint#11
Open
mcandre wants to merge 1 commit intocharlesjolley:masterfrom
mcandre:master
Open
Looked for trouble spots with JSHint#11mcandre wants to merge 1 commit intocharlesjolley:masterfrom mcandre:master
mcandre wants to merge 1 commit intocharlesjolley:masterfrom
mcandre:master
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JSHint is a nice little tool for looking for potential sources of bugs in JavaScript code. I ran
jshint .to look for things to improve on. There were a few warnings in the generated code files, but I was able to hide them all by including a.jshintignore. I'm happy to report that your code passes the current version of JSHint 100%, with no warnings whatsoever!