To start off with I just used the Prettier VSCode extension which I could just run over code that I'm working on. It formats all code very clean, easy to read format. It's an opinionated code formatter who's opinion I happen to strongly agree with. My absolute favourite code formatter is Prettier! I've used Prettier on every single JavaScript project I've created at home and at work. The answer was to automatically enforce (not just recommend) by using a collection of formatters/linters. So I began thinking of ways that I could encourage adherence to formatting/quality standards without having to point them out or fix them myself. I try to avoid doing so as I don't think it should be part of the code review - everyone knows how frustrating it is to have formatting issues pointed out. While reviewing pull requests, I find myself sometimes pointing out code formatting (inconsistent spacing, incorrect indentation, etc) and quality issues (using any, using var etc). This is probably an artifact of me always using formatters and linters in my projects, so it's become a personal standard of mine to make sure these things are done correctly. When reviewing code, I'm very particular about how code is formatted and it's quality. At work, I've spun up a handful of React projects that have a number of engineers working on it (onshore and offshore).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |