Change --stdin-filename to relative to check by .eslintignore (fixes #46)

[roadhump]

I suppose that the most common scenario is to have one .eslintignore at the root of project and execute eslint . or eslint folder/file there. That is the behavior I keep in mind to make .eslintignore settings work for plugin. That's why now plugin executes

cat /path/to/projectFolder/projectSubFolder/file | eslint --stdin --stdin-filename projectSubFolder/file

instead of

cat /path/to/projectFolder/projectSubFolder/file | eslint --stdin --stdin-filename /path/tp/projectFolder/projectSubFolder/file

or

cat /path/to/projectFolder/projectSubFolder/file | eslint --stdin --stdin-filename file

It makes to work the default .eslintignore option node_modules/**.

To revert this behavior (if full name of file in --stdin-filename is critical) add

{
    "linters": {
        "eslint": {
            "args": ["--stdin-filename", "@"]
        }
    }
}

to your .sublimelinterrc file

[tschaub]

This is a very nice enhancement. Thanks!

[caub]

How to add this

{
    "linters": {
        "eslint": {
            "args": ["--stdin-filename", "@"]
        }
    }
}

in SublimeLinter.sublime-settings for example, to avoid a .sublimelinterrc file per project

anyway I can't seem to find a way to make eslint-plugin-import work with SublimeLinter (I use SublimeLinter-contrib-eslint_d with it).

Edit: import-js/eslint-plugin-import#540 made it