@stalfh233/omc-cli 0.4.58 → 0.4.59

package/dist/compute.js

@@ -62,7 +62,27 @@ export async function cmdCompute(args) {
     catch (error) {
         return invalid(error instanceof Error ? error.message : String(error));
     }
-    const { result, exitCode } = await runToolCall("datarule.create", { args: createArgs, requestId: request, environment });
+    // Live 2026-10-20 (purchase-request app): a child-table target
+    // (schemaCode = 子表 code) made datarule.create throw, and the uncaught error
+    // surfaced as `{"code":"internal","message":"command failed"}` — no way to tell
+    // whether the formula, the schema, or the tool was at fault. Catch it and hand
+    // back an actionable hint; the same shape succeeds via datarule.create.
+    let result;
+    let exitCode;
+    try {
+        ({ result, exitCode } = await runToolCall("datarule.create", { args: createArgs, requestId: request, environment }));
+    }
+    catch (error) {
+        const message = error instanceof Error ? error.message : String(error);
+        writeEnvelope(envelope("error", {}, request, {
+            code: "compute-write-failed",
+            message: `compute 调用 datarule.create 失败：${message}\n` +
+                "若 --schema 是**子表 code**（子表列计算），改用可跑样例直接发：omc describe datarule.create --example field-compute-child-column，" +
+                "或 omc call datarule.create --args '<该样例 args>'（含 resultType/formulaType/expression 的嵌套 JSON）。",
+            retryable: false,
+        }));
+        return CLI_EXIT_CODES.internal;
+    }
     const classified = classifyResult(result);
     writeEnvelope(envelope(classified.status, result, request, classified.error));
     return exitCode;

package/dist/lanes/list-view-shapes.js

@@ -45,7 +45,15 @@ const QUERY_FILTER_TYPES = new Set(QUERY_FILTER_TYPE);
  * (`QueryFilterType.getDefaultQueryFilterType`, QueryFilterType.java) — used
  * when a condition omits `filterType`, so the stored row names its comparison.
  */
-function defaultQueryFilterType(propertyType) {
+function defaultQueryFilterType(propertyType, displayType) {
+    // Live 2026-10-20 (purchase-request app): a SHORT_TEXT field holding 是/否 was
+    // configured with `displayType:"SELECT"` but no `filterType`, and the property
+    // type table answered "Like" — a fuzzy match on an enum-valued column ("否"
+    // also matched text containing that character). An enumerated display control
+    // (SELECT/RADIO/CHECKBOX) is a closed value set, so its operator is Eq.
+    const display = typeof displayType === "string" ? displayType.toUpperCase() : undefined;
+    if (display === "SELECT" || display === "RADIO" || display === "CHECKBOX")
+        return "Eq";
     switch (propertyType) {
         case FIELD_PROPERTY_TYPES.LOGICAL:
         case FIELD_PROPERTY_TYPES.WORK_SHEET:
@@ -818,7 +826,7 @@ export function normalizeConditions(conditions, fieldRows, schemaCode) {
                 value: requestedFilterType,
                 message: `conditions 的 filterType "${String(requestedFilterType)}" 不是平台 QueryFilterType；可选：${QUERY_FILTER_TYPE.join(" / ")}`,
             });
-        row.filterType = requestedFilterType !== undefined ? String(requestedFilterType) : defaultQueryFilterType(propertyType);
+        row.filterType = requestedFilterType !== undefined ? String(requestedFilterType) : defaultQueryFilterType(propertyType, condition.displayType);
         if (condition.displayType !== undefined)
             row.displayType = DISPLAY_TYPE.index[condition.displayType] ?? null;
         if (condition.defaultValue !== undefined)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.58",
+  "version": "0.4.59",
   "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
   "type": "module",
   "bin": {
@@ -50,9 +50,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@stalfh233/omc-fake-platform": "0.4.58",
+    "@stalfh233/omc-fake-platform": "0.4.59",
     "commander": "14.0.3",
-    "omc-core": "0.4.58",
+    "omc-core": "0.4.59",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",

package/skills/omc-write-hazards.md

@@ -89,6 +89,18 @@ omc call field.publish --env local --args '{"schemaCode":"expense"}'
 
 父 `CHILD_TABLE` 行不接受 `options/choices/subFields` 更新；子列直接走上面的 CRUD 面。
 
+- **提交/审批都不要再回传子表数组**（真机 2026-10-19/20）：`data.save` 建草稿后 `data.submit` 若带子表行（无 `id`），平台按新增追加（3→9）；**审批提交同样**——`data.submit` 带 `workItemId`+`agree` 推进一步时回传子表，每级再 +1 行（1→2→3）。金额若显式传了合计不会翻倍，但行数与 SUM 口径已被污染，且没有报错。审批只回传标量字段（`agree`/意见/被改标量）；确需改子行时带 `id`+`rowStatus:"Modified"`。验收加一条"审批后子表行数不变"。
+
+## 写调用纪律
+
+- **同一 `<env>` 的写调用必须串行发起**：`write-lock-held` 不只在"并行重放失败请求"时出现，也会在**并行发起两个无关写**时触发（实测：并行两条 `dictionary.save`、并行 `field.update`+`field.publish` 各失败一次）。读可并行，写不要。
+
+## 计算规则（datarule）的取值时机
+
+- **计算由门户前端执行，API 写入不回填**：`datarule.create` 接受 `IF({实际日期}>{需求日期},"是","否")` 这类比较式并落库，但 `data.save`/`data.submit` 不计算结果值，读回仍是 null。
+- 所以"计算规则是否生效"**无法用 API 判定**，必须在门户录一条看结果；验收清单要写"计算类字段前台确认"。
+- 需要服务端就有值（参与汇总、流程分流、超期判定）时不要依赖 datarule：改用二开接口在保存/审批时算好并回写标量。
+
 ## 规则与业务集成
 
 - 规则节点缺 `nodeName` 时 CLI 按平台 `RuleNodeType` 补默认名并给 warning；业务节点优先显式命名。