{"id":2341,"date":"2018-01-21T23:48:38","date_gmt":"2018-01-22T04:48:38","guid":{"rendered":"http:\/\/osric.com\/chris\/accidental-developer\/?p=2341"},"modified":"2018-01-21T23:48:38","modified_gmt":"2018-01-22T04:48:38","slug":"using-jshint-with-travis-ci","status":"publish","type":"post","link":"https:\/\/osric.com\/chris\/accidental-developer\/2018\/01\/using-jshint-with-travis-ci\/","title":{"rendered":"Using jshint with Travis CI"},"content":{"rendered":"

I thought I’d give Travis CI<\/a> a try. It’s a tool that hooks into GitHub and runs automated tests on your code every time you push a commit. I found a straightforward tutorial<\/a> that basically said I’d need 2 files in addition to my existing code:<\/p>\n

    \n
  1. .travis.yml<\/code><\/li>\n
  2. package.json<\/code><\/li>\n<\/ol>\n

    Simple! I configured Travis CI to run JSHint<\/a> (a Javascript code linter, similar to JSLint<\/a>) on the Javascript files in my Simple Steganography<\/a> project.<\/p>\n

    I pushed a commit and discovered my files did not pass JSHint. However, I thought they should be. My files were previously configured for JSLint, and JSHint can read JSLint directives. At the top of my Javascript files I had the directives:<\/p>\n

    \/*jslint
    \n bitwise, browser
    \n*\/<\/code><\/p>\n

    These indicate that bitwise operators should be allowed, and to assume the code is running in a web browser.<\/p>\n

    JSHint (via Travis-CI) reported the following errors:<\/p>\n

    js\/decode.js: line 3, col 1, Bad option value.
    \njs\/decode.js: line 3, col 1, Bad option value.<\/code><\/p>\n

    The JSHint docs on inline configuration<\/a> indicate that the formatting should be option: Boolean<\/code>, so I reformatted the configuration directives:<\/p>\n

    \/*jslint
    \n bitwise: false,
    \n browser: true
    \n*\/<\/p>\n

    JSHint (via Travis-CI) reported several errors regarding bitwise operators:<\/p>\n

    js\/encode.js: line 179, col 37, Unexpected use of '&'.
    \njs\/encode.js: line 179, col 42, Unexpected use of '^'.
    \njs\/encode.js: line 179, col 53, Unexpected use of '&'.
    \njs\/encode.js: line 180, col 51, Unexpected use of '|'.
    \njs\/encode.js: line 182, col 51, Unexpected use of '&'.<\/code><\/p>\n

    I changed the JSHint configuration directives to:<\/p>\n

    \/*jslint
    \n bitwise: true,
    \n browser: true
    \n*\/<\/p>\n

    This worked, and my JSHint tests passed! I added a build status image to my GitHub repo:
    \n\"GitHub<\/p>\n

    The page describing the JSHint Options<\/a> definitely leads me to believe that enabling<\/em> the bitwise option would enforce<\/em> bitwise errors. This is the opposite of the behavior I’m seeing. The problem is either with the documentation, the behavior, or my reading comprehension! I opened a GitHub issue on the JSHint project<\/a> describing what I experienced.<\/p>\n","protected":false},"excerpt":{"rendered":"

    I thought I’d give Travis CI a try. It’s a tool that hooks into GitHub and runs automated tests on your code every time you push a commit. I found a straightforward tutorial that basically said I’d need 2 files in addition to my existing code: .travis.yml package.json Simple! I configured Travis CI to run … Continue reading Using jshint with Travis CI<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[56],"tags":[482,479,480,481],"class_list":["post-2341","post","type-post","status-publish","format-standard","hentry","category-testing","tag-github","tag-jshint","tag-jslint","tag-travis-ci"],"_links":{"self":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/2341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/comments?post=2341"}],"version-history":[{"count":4,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/2341\/revisions"}],"predecessor-version":[{"id":2346,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/2341\/revisions\/2346"}],"wp:attachment":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/media?parent=2341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/categories?post=2341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/tags?post=2341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}