Make the rule fixable

[gajus]

It would be nice if this plugin/rule was able to fix itself.

[michaeljonathanblack]

Ah shoot, that's the only reason I was going to pull this library. I wanted to eslint --fix a file that has way too many functions and isn't sorted in any logical way.

[gajus]

@channikhabra has written a brilliant utility for that https://github.com/channikhabra/js-sort-object-properties

[michaeljonathanblack]

Thanks gajus!

[michaeljonathanblack]

I spoke too soon, I couldn't get that to work on anything complex... Works great on the example code, though!

[gajus]

@mherodev best to raise an issue where the author can see, https://github.com/channikhabra/js-sort-object-properties/issues

[davidpfahler]

I would be extremely helpful if this did fix itself. Otherwise it really isn't practical.
I would gladly help making this possible, though I really can't find a clue how to attempt this.

---

Hey all, I dove into this a bit and it seems this is not possible with the current fixer in ESLint. I think a babel plugin would be the better choice here.

[jacobrask]

You might be able to do something with jscodeshift, inspired by https://github.com/reactjs/react-codemod/blob/master/transforms/sort-comp.js

[davidpfahler]

@jacobrask Thank you. I'm still looking into this. For performance reasons, especially during dev, I'd like to avoid parsing the code twice. For reference, these discussion in eslint issues might be relevant: eslint/eslint#5329 estree/estree#41