Revert prettier upgrade and fix formatting #7891
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bduffany
force-pushed
the
prettier-reformat
branch
2 times, most recently
from
e086b05
to
048a74a
Compare
bduffany
force-pushed
the
prettier-reformat
branch
from
048a74a
to
53ee2d8
Compare
bduffany
changed the title
tempoz
approved these changes
Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The version upgrade in #7741 is causing unexpected prettier diffs whenever we change certain files. This is because prettier 3.x introduced new formatting rules, but our prettier script only checks/formats changed files. So, in the upgrade PR, Checkstyle didn't complain about the formatting now being incorrect after the upgrade, and the latent formatting errors are being surfaced in PRs only as the files are edited.
This PR reverts prettier back to 2.1.1 and updates Checkstyle to catch this error in CI - if the prettier version in yarn.lock changes, then all files are checked/formatted, not just changed files.