I just wrote a PR that didn’t pass the Travis tests due to linting issues. I couldn’t find any entries in meta that discussed eslinting/prettier, so I went digging around the code and found out how to improve my code to fit with the styling and listing standards of Discourse. This may be useful for …

I personally use Sunsetting Atom - The GitHub Blog which automatically fix the errors on save and Sunsetting Atom - The GitHub Blog which provides JIT notifications on whether I broke any eslint rules.

Rubocop is related but not the same thing, we should definitely add nice links to the op pointing at each other

I recommend installing overcommit which adds hooks to your git repository and runs the linters (Rubocop and EsLint) on changed files before each commit.

It doesn’t run prettier though :frowning:

It could be added: https://github.com/juriewessels/overcommit-prettier But I haven’t looked into it, because my IDE is running prettier. :wink:

Code linting and formatting with prettier

개발

pfaffman (Jay Pfaffman) 7월 24, 2018, 5:14오전 2

I think you’re looking for Rubocop has landed on Discourse 👮‍♀️ 👮.

글		댓글	조회수
Prettier : code formatting tool Development	4	6409	6월 3, 2019
Help configuring rubocop, eslint, and so on in vscode and the command line Marketplace	2	817	8월 29, 2023
Travis tests failing due to eslint Development	7	1190	9월 10, 2020
Automatically lint and format code before commits Developer Guides how-to , code	0	1691	11월 8, 2019
Linting consistency Development	9	309	12월 2, 2025

Code linting and formatting with prettier

Related topics