Respect JSHint Configrautions

[lijunle]

According to JSHint docs, there are three ways to configure JSHint:

1. Specify with --config option
2. .jshintrc file under project hierarchy
3. package.json file under project root

And, of course, JS file inline configuration. Something like this:

/* jshint undef: true, unused: true */
/* global MY_GLOBAL */

Regarding .jshintrc configuration file, notice this sentence:

In case of .jshintrc, JSHint will start looking for this file in the same directory as the file that's being linted. If not found, it will move one level up the directory tree all the way up to the filesystem root.

But, because AtomLinter save the atom content buffer to a temporary file, it will NOT respect the above rule. Besides, AtomLinter does not expose the --config option to the end-user.

Currently, the only way to configure JSHint is to add inline directives. Once the project contains many files, this is a nightmare.

Please consider to add support to respect the JSHint rules.

[noseglid]

+1 for being able to use .jshintrc.

Implementation suggestion details:
It should be possible to use atom.workspace.getActiveEditor().getPath() to get the path of the current file. Check if path.basename(activeFile) + '.jshintrc' exists. If yes, use it, otherwise move one path up untilatom.project.getPath()` is reached. I would love to see this.

[kokarn]

+1 if anyone feels like looking into this

[gluxon]

This seems to work already. My .jshintrc configuration in the root project folder is respected.

https://github.com/AtomLinter/linter-jshint/blob/master/lib/linter-jshint.coffee#L30

[Trudko]

I would like to see setting for config option

[steelbrain]

.jshintrc and package.json both are respected now.