Consider using eslint + prettier

[core-ai-bot]

Issue by humphd
Sunday Apr 09, 2017 at 23:12 GMT
Originally opened as adobe/brackets#13290

---

In our Mozilla fork, we're thinking to move to using prettier via eslint to autoformat the code. I'm working with lots of new contributors, and trying to get them to style commits properly is a losing battle. I'm of the mind that doing this with tooling is the better way going forward.

Before we do it, I thought I'd see if you had interest here first; if so, it will make merging easier. Since you've not switched to eslint, this might make sense.

If it doesn't hold interest for you, let me know and we can close this.

[core-ai-bot]

Comment by petetnt
Monday Apr 10, 2017 at 11:04 GMT

---

Actually we have already switched to eslint a long while back and I wouldn't have any issues myself to use prettier in combination too. 👍

[core-ai-bot]

Comment by humphd
Thursday Apr 13, 2017 at 13:59 GMT

---

@dsych is starting this work in mozilla/brackets#703. I made a compare branch to show the effect of running grunt eslint using prettier to fix problems. There are some things here that need to be adjusted (e.g., 4-spaces vs. 2, fix javadoc style comment blocks, etc) but everything is configurable. Feel free to chime in with any suggestions on how the configuration should look.

Should I have him move this PR here, or keep it in ours?