Thanks for the good manual!
Could you clarify, please, what is the real profit of using prettier? What prettier does that eslint does not. I'm using eslint without prettier connected for a long time and it covers all our formatting needs. I see the notice, that prettier is optional. So is it really worth it to install one more additional package?
⭐️ This is a very good question. I know the answer for it and I am writing one small article on this and I will post the link once done. Thanks for dropping by.
I'm Cássio Freitas from Brazil (🇧🇷). I started my career as Marketing Analyst and Digital Traffic Manager in 2015, and I am currently Code Cadet of the 52nd class of the Academia de Código.
This is probably considered necromancy; but seeing as you didn't get a complete answer and for the benefit of others:
Prettier is particularly useful when working in teams. If each person has a subtly different coding style, then simple changes in formatting can result in a change registered in a commit that doesn't affect the logic itself. That adds unnecessary noise to commits. Prettier avoids this by enforcing agreed formatting patterns.
You then have confidence that when reviewing commits - e.g. during code review or bug-fixing - you're seeing changes to logic and not formatting.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the good manual!
Could you clarify, please, what is the real profit of using prettier? What prettier does that eslint does not. I'm using eslint without prettier connected for a long time and it covers all our formatting needs. I see the notice, that prettier is optional. So is it really worth it to install one more additional package?
⭐️ This is a very good question. I know the answer for it and I am writing one small article on this and I will post the link once done. Thanks for dropping by.
This is probably considered necromancy; but seeing as you didn't get a complete answer and for the benefit of others:
Prettier is particularly useful when working in teams. If each person has a subtly different coding style, then simple changes in formatting can result in a change registered in a commit that doesn't affect the logic itself. That adds unnecessary noise to commits. Prettier avoids this by enforcing agreed formatting patterns.
You then have confidence that when reviewing commits - e.g. during code review or bug-fixing - you're seeing changes to logic and not formatting.