Repository navigation
chore(oxfmt.config): replace '.oxfmtrc.json' with 'oxfmt.config.ts' - #11944
Conversation
|
|
View your CI Pipeline Execution ↗ for commit 75a7724
☁️ Nx Cloud last updated this comment at |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe formatter configuration moved from ChangesOxfmt Configuration Migration
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Refactor Suggested reviewers: Merge Risk: ⚪ Minimal · up to The formatter configuration retains its prior behavior, and no concrete formatter or labeler-generation failure is established. The change is ready for normal merge checks. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 Changeset Version Preview2 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
size-limit report 📦
|
🎯 Changes
Move the oxfmt config to TypeScript, in line with
oxlint.config.ts..oxfmtrc.jsonwithoxfmt.config.tsusingdefineConfig, with the same options and ignore patterns.$schemais dropped becausedefineConfigprovides the types. oxfmt discoversoxfmt.config.tson its own.scripts/generate-labeler-config.tsimports the config instead of reading and parsing.oxfmtrc.json.oxfmt --check .passes on the same set of files as before, and the generated labeler config is identical.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit