Fix inconsistencies between local and remote formatters #634
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.
Local formattter configuration
We use
husky
to configure pre-commit hooks so files are automatically linted and formatted withlint-staged
on each commit. Unfortunately,prettier
is not being used for files with thejs
extension due to a misconfiguration.cml/package.json
Lines 47 to 51 in 1ed743d
cml/package.json
Lines 52 to 59 in 1ed743d
Remote formattter configuration
Here we use
prettier
for all the extensions above plus thejs
andjson
ones. That's the issue behind #623 and company.cml/.restyled.yaml
Lines 1 to 8 in 1ed743d