| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
🦋 Changeset detectedLatest commit: 0a18559 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 73.43358% with 106 lines in your changes missing coverage. Please review. @@ Coverage Diff @@
## next #1744 +/- ##
==========================================
+ Coverage 80.59% 80.60% +0.01%
==========================================
Files 66 66
Lines 5360 5363 +3
Branches 1026 1025 -1
==========================================
+ Hits 4320 4323 +3
Misses 1033 1033
Partials 7 7 ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. I'm for the default trailing comma setting too, though given we still need to merge main into next for time to time, maybe we should hold back for now until next is nearly ready for stable.
Sorry, something went wrong.
Their API is largely compatible between v2 and v3. We are using getPrettierInstance helper to resolve a local installation first and that, to the best of my knowledge, is compatible with both versions. So this change only changes what gets loaded by default if we can't find an already installed Prettier. |
Sorry, something went wrong.
|
after merging this i would recommend adding a .git-blame-ignore-revs file to exclude the formatting commit's changes from git and github's blames |
Sorry, something went wrong.
|
@beeequeue could you sync this with next? |
Sorry, something went wrong.
Co-authored-by: Bjorn Lu <bjornlu.dev@gmail.com>
| Back | FazBrowse Home | New Git URL |
Updates Prettier to v3.
This also means the minimum version of it as a peer dependency also gets bumped to the latest one. Maybe the peer dependency requirement should be changed to ^3?
I reverted the updated trailingCommas setting back to the v2 value to minimize the amount of formatting changes as recommended by @bluwy, but if @Andarist agrees I can revert to the default v3 config and re-format the files according to that.
(Personally I would also set the line-width to 90-100 as well, for better readability)