You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with this codebase, there are different formatting conventions in different files (e.g. tabs in tests.js and spaces in index.test.js. Having worked with Prettier in most of my projects, I can advocate for its use as a time saving tool. It formats the code automatically so that we as authors never need to think about formatting. I would suggest that we adopt Prettier in this codebase, as it will make work going forward easier.
The text was updated successfully, but these errors were encountered:
I'll admit I prefer the feature set of ESLint over Prettier, but either one would be an improvement, so I'll leave the decision up to the implementer. I'd also prefer an implementation that has the least impact on functional code (i.e. index.js). ESLint allows you to tailor the ruleset more than Prettier to my knowledge, but I'll be happy with either solution.
When working with this codebase, there are different formatting conventions in different files (e.g. tabs in tests.js and spaces in index.test.js. Having worked with Prettier in most of my projects, I can advocate for its use as a time saving tool. It formats the code automatically so that we as authors never need to think about formatting. I would suggest that we adopt Prettier in this codebase, as it will make work going forward easier.
The text was updated successfully, but these errors were encountered: