3 Commits

Author	SHA1	Message	Date
Misaka_Company	78241f2b8d	fix: component worksheet rowCount false positive validation error ... Fix critical bug in BOM matching validation: when [部件] worksheet matches 1 record but returns 2 sub-components, system incorrectly reports "matched 2 records". Root Cause: - matchResult("rowCount") incorrectly used componentMaterials.count (material count) - instead of bomMatchResult("rowCount") (worksheet row count) - Caused 1-row match returning 2 sub-components to be misreported as "2 matches" Solution: 1. M08_ComponentProcessor.ProcessComponentRecord: Add matchedRowNum parameter, receive matched row number from caller, avoid redundant internal matching 2. M09_BOMExtractor: Implement two-phase matching flow - Phase 1: Call MatchBOMRecord to get standard match result (with correct rowCount) - Phase 2: If match succeeds, call ProcessComponentRecord to process component logic - matchResult("rowCount") always uses standard match's rowCount (worksheet row count) Fix Results: - Scenario 1: [部件] matches 1 row, returns 1 component → rowCount=1 ✅ - Scenario 2: [部件] matches 1 row, returns 2 sub-components → rowCount=1 ✅ (no false positive) - Scenario 3: [部件] matches 0 rows → rowCount=0, correct error ✅ - Scenario 4: [部件] matches 2+ rows → rowCount=2, correct error ✅ Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-02-12 15:54:50 +08:00
Misaka_Company	867b1979af	refactor: improve BOM library matching logic with column-name-based lookup ... - Add BOM library column name constants (名称, 编码, 数量, etc.) - Add GetBOMConditionFields() and IsConditionField() utility functions - Refactor ExtractMaterialInfo to use column names instead of hardcoded positions - Refactor ExtractSingleSubComponent to use column names for 接头/弹性元件 - Refactor ExtractComponentInfo to use column names - Improve MatchAllMaterialTypes to iterate all worksheets dynamically - Add debug logging for troubleshooting This fix resolves issues where worksheets with non-standard column counts (like 表壳, 罩壳) could not extract material information properly. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-02-12 13:59:48 +08:00
Misaka_Company	093a2d0a3b	feat: implement BOM auto-extraction system ... Add complete BOM auto-extraction system with the following modules: - M06_ModelParser: Parse product model strings to extract parameters (azxs, bkxs, gclj, jycz, lcfw, fjgn) - Extracts header part from full model (ignores dial/attachment parts) - Splits process connection and material code (G123 -> G12, 3) - Supports multiple additional features with comma/dot separators - M07_BOMMatcher: Match materials in BOM library - Exact match, wildcard (empty cell), negative match (!=) - Special fjgn contains matching logic - Array-based performance optimization for bulk operations - M08_ComponentProcessor: Handle component material special logic - Component inventory check (interface reserved) - Sub-component extraction (joint + elastic element) - Combination validation rules (1 component OR 1 joint + 1 element) - M09_BOMExtractor: Main extraction orchestrator - Reads input models from worksheet - Processes each model and matches all material types - Outputs to "BOM提取结果" worksheet - Error reporting and non-blocking design - M06B_TestRunner: Comprehensive unit tests - 8 test cases for model parsing - 5 test cases for BOM matching - 5 test cases for component processing - M04_Config: Add BOM extraction constants - BOM library filename and configuration - Input/output column definitions - Output column enumeration - M01_Main: Add RunBOMExtraction entry point Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-02-12 13:02:14 +08:00