✨ feat(order-resolver): add deduplication logic for production order number resolution
- Add P0: DISTINCT in SQL query to prevent database duplicates
- Add P1: Input layer deduplication to avoid redundant queries
- Add P2: Return layer deduplication in getValidOrderNumbers()
- Optimize resolve() to use batch query instead of loop queries
- Add getDeduplicationReport() for human-readable mapping summary
- Improve extraction logs to show deduplication statistics
- Only log merged mappings (multiple productionIDs → one order number)
- Remove duplicate marking as error (normal business scenario)
- Bump version to 1.0.1
Example log output:
输入 5 个总排号 → 解析为 2 个唯一订单号(3 个重复已合并)
重复合并详情:
SC70202603120085 ← 26B12214、26B12213、26B12212 (共 3 个总排号)
SC70202603120131 ← 26B12125、26B12126 (共 2 个总排号)
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "erpauto",
|
||||
"version": "1.0.0",
|
||||
"version": "1.0.1",
|
||||
"description": "An Electron application with React and TypeScript",
|
||||
"main": "./out/main/index.js",
|
||||
"author": "example.com",
|
||||
|
||||
Reference in New Issue
Block a user