search

Heisenbergjs / heisenberg

A project base for building modern JavaScript applications
http://heisenbergjs.github.com/heisenberg/
156 stars 12 forks source link

Add .jshintrc #38

Closed OliverJAsh closed 11 years ago

jackfranklin commented 11 years ago

Or you pass in options directly in the Gruntfile?

OliverJAsh commented 11 years ago

Yup. Whichever is preferred!

On 24 Jan 2013, at 10:30, Jack Franklin notifications@github.com wrote:

Or you pass in options directly in the Gruntfile?

— Reply to this email directly or view it on GitHub.

jackfranklin commented 11 years ago

Cool - I don't really have a preference towards which one. Perhaps the Gruntfile so it's one less dotfile? It makes little difference.

OliverJAsh commented 11 years ago

:thumbsup:

OliverJAsh commented 11 years ago

Just thought, surely .jshintrc should be better so that the IDE recognises it too?

jackfranklin commented 11 years ago

Who uses an IDE these days?! :pager:

OliverJAsh commented 11 years ago

SublimeLinter is popular. I use it! :P https://github.com/SublimeLinter/SublimeLinter#linter-specific-notes

jackfranklin commented 11 years ago

Haha! Need to check that grunt-contrib-jshint does indeed pick up a .jshintrc file - although I'm 99% confident it will do - and yeah I'm happy to go with that.

jackfranklin commented 11 years ago

Whoever tackles #39 (currently assigned as me but anyone else, feel free :+1:) should probably tackle this at the same, they kind of go together.

OliverJAsh commented 11 years ago

Yup, the task for it would look something like this:

    jshint: {
      all: ['Gruntfile.js', 'app/scripts/**/*.js'],
      options: {
        jshintrc: './.jshintrc',
      }
    },

(Dammit, why doesn't Markdown work from email?!)