fix: require config path or file names#1
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdded an early validation check in loadConfig that throws an error if neither a path nor at least one configFileNames entry is provided. Updated the JSDoc for LoadConfigOptions to reflect that configFileNames is required when path is absent. Added a test case verifying loadConfig rejects with the appropriate error message under these conditions, including when configFileNames is an empty array. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 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 |
Summary
This PR makes
loadConfigreject calls that do not specify either a custompathor at least oneconfigFileNamesentry, avoiding silent empty configs when no search target is configured.