refactor(file): return option from extraction format parsing#10411
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 (5)
📝 WalkthroughWalkthroughThis PR refactors the ChangesExtraction Format API Refactor
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Greptile SummaryThis PR refactors
Confidence Score: 5/5All call sites correctly handle the new Each call site was updated consistently: aqua bails on unknown formats (unchanged), github and static_helpers fall back to Raw for unrecognized explicit options (unchanged), and Java's No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "refactor(file): return option from extra..." | Re-trigger Greptile |
Summary
ExtractionFormat::from_extto returnOption<ExtractionFormat>instead of silently falling back toRawRawwhere they already didand_thenfor recognized file typesTests
cargo fmtcargo test test_extraction_format_from_file_namecargo test effective_extraction_formatcargo checkSummary by CodeRabbit