This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
chore: Fix prettier inconsistencies from duplicate versions #651
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.
After #613, we had two different versions of
prettier
in the lockfile. One of them was being used for IDE save andprettier --write
, and a different one was being used forlint-staged
. This led to random unintended formatting changes like in #636 (comment) and #648 (comment).So I deduped the prettier versions in our lockfile and ran
yarn prettier
against the repo and also verified thatlint-staged
doesn't break anything on committing. The only resulting formatting change is inComboBox.tsx
, reverting the unintended one from #636.