Use cwd for create eslint fix

[lewisl9029]

This seems to fix prettier/prettier-atom#505

Previously we weren't specifying a cwd option for eslint in createEslintFix, so the working directory defaulted to where prettier-atom invoked the function, i.e. somewhere in the atom config directory. This ensures we infer the cwd from the filePath as we do in getESLintConfig here: https://github.com/prettier/prettier-eslint/blob/master/src/index.js#L227

The change seems to have broken this test assertion expecting 2 calls to readFileSync: d9d190e#diff-8a18675f0cf6827722b5896d753397b9L356

I updated the test here but wasn't fully sure of the implications. Let me know if this is problematic. Would love to hear other suggestions on how to move forward with this bugfix.

[lewisl9029]

@zimme mind taking a look at this one?

It's meant to fix the most popular issue on prettier-atom with 33 👍 s and 39 comments, affecting a lot of people: prettier/prettier-atom#505

And the fix itself is fairly small: https://github.com/prettier/prettier-eslint/pull/242/files#diff-1fdf421c05c1140f6d71444ea2b27638R173

Thanks!

[jjosef]

This looks good to me!

[jjosef]

Is anyone maintaining this project? This is a serious issue.

[SebiTimeWaster]

is there maybe a usable fork of this project that has this fix?

[SebiTimeWaster]

there was no activity in 1 month on this project, i think it is dead.

[jjosef]

Probably a good idea. I am unable to at the moment but would be nice to see this happen

[zimme]

Will look into this later this week when I'll look into the eslint 6 stuff, if my family life permits me some spare time

[louisscruz]

Any update on this? I've just verified that this does in fact solve prettier/prettier-atom#505.

[digitalmaster]

Should we fork this plugin?

[j-f1]

cc @prettier/eslint

[zimme]

Merged in 6d4fb22 with some changes.

Please test 9.0.1 and see if this is solved.