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 prettier-atom which automatically fix the errors on save and linter-eslint 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:

Prettier によるコードのリンティングとフォーマット

開発

pfaffman (Jay Pfaffman) 2018 年 7 月 24 日午前 5:14 2

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

トピック		返信	表示
Prettier : code formatting tool Development	4	6362	2019 年 6 月 3 日
Help configuring rubocop, eslint, and so on in vscode and the command line Marketplace	3	750	2023 年 9 月 28 日
Travis tests failing due to eslint Development	8	1150	2020 年 9 月 12 日
Automatically lint and format code before commits Developer Guides how-to , code	1	1460	2026 年 3 月 13 日
Linting consistency Development	10	169	2026 年 1 月 1 日

Prettier によるコードのリンティングとフォーマット

関連トピック