“I don’t want anybody to nitpick any other person ever again.”.“Having a githook set up has reduced the amount of style issues in PRs that result in broken builds due to ESLint rules or things I have to nit-pick or clean up later.”.“Our top reason was to stop wasting our time debating style nits.”.
#CODE PRETTIER HOW TO#
It’s far easier for us all to agree now: just run Prettier, and go with that style.” It was dumb, but it was a weird on-going “great debate” that wasted lots of little back and forth bits. “Literally had an engineer go through a huge effort of cleaning up all of our code because we were debating ternary style for the longest time and were inconsistent about it.While sometimes fruitful, these discussions are for the most part wasteful.” “We want to free mental threads and end discussions around style.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? So why choose the “Prettier style guide” over any other random style guide? Because Prettier is the only “style guide” that is fully automatic. People get very emotional around particular ways of writing code and nobody likes spending time writing and receiving nits. 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. By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles.
0 kommentar(er)
