Add prettier formatter with basic configuration options #140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces an opinionated coding formatter configuration using Prettier. The biggest reason for adopting Prettier is to stop all the ongoing debates over styles and provide consistency across styles and scripts. The implementation is straightforward, requiring only periodic running of the
npm run precommit
command to enforce the coding style. Including Prettier in the dev dependencies also ensures that all contributors can use it regardless of their chosen IDE.Here's the current configuration:
Please note that we will also need to keep the
.editorconfig
file up-to-date and ensure that both configurations are aligned.This pull request focuses solely on the introduction of a formatter, and does not include a linter. The naming of the branch may suggest otherwise, but adding a linter is a separate matter that will be addressed in a future pull request.