-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: populate existing cspell.json words during migration #1208
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1208 +/- ##
==========================================
+ Coverage 94.33% 94.73% +0.39%
==========================================
Files 99 103 +4
Lines 5666 5715 +49
Branches 462 473 +11
==========================================
+ Hits 5345 5414 +69
+ Misses 320 300 -20
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Test failures are unrelated. #877 |
🎉 This is included in version v1.54.0 🎉 The release is available on: Cheers! 📦🚀 |
PR Checklist
status: accepting prs
Overview
Runs
pnpm lint:spelling
and matchesUnknown word (...)
complaints.Also standardizes two things in code that were bugging me:
node:fs/promises
imports asimport * as fs
formatJson
instead of manuallyprettier.format
callsThis finally means that the file creator for
cspell.json
no longer needs to prepopulate with a static list of words. So unnecessary ignored words will no longer be potentially introduced by that. Yay.