From ff4ef426e638398259a4611d77954ba6be495f72 Mon Sep 17 00:00:00 2001 From: Barbara He Date: Wed, 5 Sep 2018 15:11:24 -0700 Subject: [PATCH] added link to style guideline benefits, fixed issue #4894 (#5062) --- docs/why-prettier.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/why-prettier.md b/docs/why-prettier.md index 3838ffdc..bee7c307 100644 --- a/docs/why-prettier.md +++ b/docs/why-prettier.md @@ -5,7 +5,7 @@ title: Why Prettier? ## Building and enforcing a style guide -By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. It is generally accepted that having a common style guide is valuable for a project and team but getting there is a very painful and unrewarding process. People get very emotional around particular ways of writing code and nobody likes spending time writing and receiving nits. +By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. [It is generally accepted that having a common style guide is valuable for a project and team](https://www.smashingmagazine.com/2012/10/why-coding-style-matters/) but getting there is a very painful and unrewarding process. People get very emotional around particular ways of writing code and nobody likes spending time writing and receiving nits. So why choose the "Prettier style guide" over any other random style guide? Because Prettier is the only "style guide" that is fully automatic. Even if Prettier does not format all code 100% the way you'd like, it's worth the "sacrifice" given the unique benefits of Prettier, don't you think?