openxiangda 1.0.16 → 1.0.18

package/openxiangda-skills/SKILL.md

@@ -69,6 +69,8 @@ When the user provides a root domain such as `https://yida.wisejob.cn/`, use it
 - Publish normal form pages, workflow form pages, and custom code pages through `openxiangda workspace publish --profile <name>` from the app workspace.
 - Never store token data in the project directory. User tokens live in `~/.openxiangda/profiles.json`; project state lives in `.openxiangda/state.json` and stores only IDs and mappings.
 - Use logical resource codes in local files. Platform-specific IDs such as `formUuid`, `pageId`, `workflowId`, and `automationId` must be isolated by profile.
+- Put engineering-managed resources in `src/resources/` and use `openxiangda resource validate|plan|publish|pull`. `workspace publish` publishes workspace forms/pages first, then runs non-destructive resource upsert. Only pass `--prune` when the user explicitly wants local manifests to delete platform-side extras.
+- For external APIs, create a connector manifest in `src/resources/connectors/` and call it from pages through `sdk.connector`; never put third-party API keys in page source.
 - Before publishing to another platform, verify the workspace is bound for that profile. Resource IDs from one profile must not be reused for another profile.
 - Use `openxiangda app snapshot <APP_XXX> --profile <name> --json` for diagnosis before changing an existing app.
 - Run write commands that update `.openxiangda/state.json` sequentially within the same workspace. Read-only commands can run in parallel.
@@ -100,6 +102,7 @@ Core CLI / state:
 
 - `references/openxiangda-api.md` — `/openxiangda-api/v1` request and response fields.
 - `references/workspace-state.md` — `.openxiangda/state.json` shape and profile isolation rules.
+- `references/connector-resources.md` — `src/resources` manifests, connector schema, and SDK connector calls.
 
 Form authoring:
 

package/openxiangda-skills/references/connector-resources.md

@@ -0,0 +1,68 @@
+# Connector Resources
+
+OpenXiangda engineering resources live under `src/resources/`.
+
+Common folders:
+
+- `connectors`
+- `roles`
+- `menus`
+- `workflows`
+- `automations`
+- `permissions/page-groups`
+- `permissions/form-groups`
+- `settings/forms`
+
+Commands:
+
+```bash
+openxiangda resource validate --profile dev
+openxiangda resource plan --profile dev
+openxiangda resource publish --profile dev
+openxiangda resource pull --profile dev
+```
+
+Connector manifests use stable `code` values. The platform maps connector `code` to the existing connector `methodName`, and API `code` to the existing connector API `methodName`.
+
+```json
+{
+  "code": "crm",
+  "name": "CRM Service",
+  "url": "https://crm.internal.example.com/api",
+  "authType": "apiKey",
+  "authConfig": {
+    "apiKey": {
+      "key": "X-API-Key",
+      "value": "internal-secret",
+      "in": "header"
+    }
+  },
+  "userContext": {
+    "enabled": true,
+    "inject": [
+      { "target": "header", "key": "X-User-Id", "value": "userId" },
+      { "target": "body", "key": "operator", "value": "user" }
+    ]
+  },
+  "apis": [
+    {
+      "code": "getCustomer",
+      "name": "Get Customer",
+      "method": "POST",
+      "path": "/customers/search",
+      "requestBodyType": "json",
+      "responseType": "json"
+    }
+  ]
+}
+```
+
+Runtime page code:
+
+```ts
+await sdk.connector.call("crm.getCustomer", {
+  body: { keyword: "Acme" },
+})
+```
+
+Do not put third-party domains or API keys in page source. The runtime page calls `/:appType/v1/connectors/actions/invoke` for normal responses and `/:appType/v1/connectors/actions/download` for binary downloads; the platform backend applies auth, user context, and redaction.

package/openxiangda-skills/references/pages/page-sdk.md

@@ -6,6 +6,7 @@ Guidelines:
 
 - Do not hardcode `/openxiangda-api` calls inside end-user page components unless the page is explicitly an admin tool.
 - Prefer SDK modules for form data, user context, permissions, and platform navigation.
+- Use `sdk.connector.invoke`, `sdk.connector.call("connector.api")`, or `sdk.connector.download` for external services. The SDK calls the platform runtime connector endpoint; it must not call third-party domains directly.
 - For the current user's department hierarchy, use `sdk.department.getCurrentUserParentDepartments()`; do not hardcode `GET /department/:id/parentDepartments` in page code.
 - Keep API calls behind small local functions so generated UI stays testable.
 - Treat user context and tenant context as runtime-provided values.

package/openxiangda-skills/references/workspace-state.md

@@ -28,7 +28,12 @@ Tokens never belong in the project. User tokens live in `~/.openxiangda/profiles
         },
         "workflows": {},
         "automations": {},
-        "menus": {}
+        "menus": {},
+        "roles": {},
+        "connectors": {},
+        "pagePermissionGroups": {},
+        "formPermissionGroups": {},
+        "formSettings": {}
       }
     }
   }
@@ -40,6 +45,7 @@ Tokens never belong in the project. User tokens live in `~/.openxiangda/profiles
 - Profile is the deployment boundary.
 - `baseUrl` is the backend API base. On standard private deployments it is `<origin>/service`; management pages use `/platform`, and app runtime pages use `/view`.
 - Local resource keys are logical codes.
-- Live IDs are nested under the profile that produced them.
+- Live IDs and lightweight runtime aliases are nested under the profile that produced them.
+- Do not store business configuration or secrets in `.openxiangda/state.json`; store those in `src/resources/`.
 - A prod publish must not read dev IDs.
 - Before publishing to another platform, run `openxiangda workspace bind --profile <name> --app-type <APP_XXX>`.

package/openxiangda-skills/skills/openxiangda-core/SKILL.md

@@ -60,6 +60,8 @@ openxiangda workspace bind --profile dev --app-type APP_DEV
 openxiangda workspace bind --profile prod --app-type APP_PROD
 cd /path/to/sy-lowcode-app-workspace
 openxiangda workspace publish --profile dev
+openxiangda resource validate --profile dev
+openxiangda resource plan --profile dev
 ```
 
 Read-only diagnosis can use resource commands:
@@ -93,8 +95,10 @@ Project state is stored in `.openxiangda/state.json`:
         "automations": {},
         "menus": {},
         "roles": {},
+        "connectors": {},
         "pagePermissionGroups": {},
-        "formPermissionGroups": {}
+        "formPermissionGroups": {},
+        "formSettings": {}
       }
     }
   }

package/openxiangda-skills/skills/openxiangda-page/SKILL.md

@@ -60,3 +60,6 @@ Read these references only when editing page code:
 - For list / detail / CRUD pages, follow `../../references/architecture-patterns.md` (e.g. `DataManagementList`) before writing custom data-fetching loops.
 - Pick components per `../../references/component-guide.md`: prefer the platform component, fall back to Ant Design, and only build a custom component when neither fits.
 - When a page misbehaves (lost styles, `options is undefined`, option labels showing raw values, etc.), consult `../../references/troubleshooting.md` before patching symptoms.
+- For custom portal pages and business modals, do not temporarily embed a single `FormProvider` field component from the standard form runtime. If a standard component is required, navigate to a full standard form page or render a complete `StandardFormPage` inside a dedicated carrier route.
+- Keep PC and mobile portal styles separate. Do not share one form UI implementation across both viewports unless the surrounding shell, modal layer, date picker, and bottom-sheet behavior have been tested in both contexts.
+- After introducing Ant Design overlays, date/datetime fields, or mobile bottom-sheet selectors, verify that global button, modal, picker, and sheet styles do not leak into the host business page.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.16",
+  "version": "1.0.18",
   "description": "OpenXiangda CLI, workspace build tools, runtime SDK, and form components.",
   "private": false,
   "bin": {
@@ -54,6 +54,7 @@
     "check": "node --check bin/openxiangda.js && node --check lib/*.js && node --check packages/sdk/src/build-source/src/cli.mjs && node --check packages/sdk/src/build-source/scripts/*.mjs && node --check packages/sdk/src/build-source/scripts/utils/*.mjs",
     "prepack": "npm run build:sdk",
     "test:profile-isolation": "bash scripts/profile-isolation-smoke.sh",
+    "test:resource-plan": "node scripts/resource-plan-smoke.mjs",
     "test:skill-install": "bash scripts/skill-install-smoke.sh",
     "test:workspace-init": "bash scripts/workspace-init-smoke.sh"
   },

package/packages/sdk/dist/components/index.cjs

@@ -31713,26 +31713,35 @@ var secondOptions = Array.from({ length: 60 }, (_, second) => ({
   label: `${second}\u79D2`,
   value: pad2(second)
 }));
-function formatMobileTime(date4) {
-  return (0, import_dayjs12.default)(date4).format("HH:mm:ss");
+function resolveTimePickerPrecision(dateFormat) {
+  return dateFormat && /s/i.test(dateFormat) ? "second" : "minute";
 }
-function getTimePickerValue(date4) {
-  return [(0, import_dayjs12.default)(date4).format("HH"), (0, import_dayjs12.default)(date4).format("mm"), (0, import_dayjs12.default)(date4).format("ss")];
+function formatMobileTime(date4, dateFormat) {
+  return (0, import_dayjs12.default)(date4).format(resolveTimePickerPrecision(dateFormat) === "second" ? "HH:mm:ss" : "HH:mm");
 }
-function applyTimePickerValue(base, value) {
+function getTimePickerColumns(precision = "second") {
+  return precision === "second" ? [hourOptions, minuteOptions, secondOptions] : [hourOptions, minuteOptions];
+}
+function getTimePickerValue(date4, precision = "second") {
+  const base = [(0, import_dayjs12.default)(date4).format("HH"), (0, import_dayjs12.default)(date4).format("mm")];
+  return precision === "second" ? [...base, (0, import_dayjs12.default)(date4).format("ss")] : base;
+}
+function applyTimePickerValue(base, value, precision = "second") {
   const [hour, minute, second] = value;
-  return (0, import_dayjs12.default)(base).hour(Number(hour ?? 0)).minute(Number(minute ?? 0)).second(Number(second ?? 0)).millisecond(0).toDate();
+  return (0, import_dayjs12.default)(base).hour(Number(hour ?? 0)).minute(Number(minute ?? 0)).second(precision === "second" ? Number(second ?? 0) : 0).millisecond(0).toDate();
 }
 function MobileTimePickerView({
   value,
+  dateFormat,
   onChange
 }) {
+  const precision = resolveTimePickerPrecision(dateFormat);
   return /* @__PURE__ */ (0, import_jsx_runtime34.jsx)(
     picker_view_default,
     {
-      columns: [hourOptions, minuteOptions, secondOptions],
-      value: getTimePickerValue(value),
-      onChange: (nextValue) => onChange(applyTimePickerValue(value, nextValue)),
+      columns: getTimePickerColumns(precision),
+      value: getTimePickerValue(value, precision),
+      onChange: (nextValue) => onChange(applyTimePickerValue(value, nextValue, precision)),
       className: "sy-mobile-time-picker",
       renderLabel: (item) => item.label
     }
@@ -31769,30 +31778,32 @@ function getDateOptions(center, min2, max2) {
     };
   });
 }
-function getDateTimePickerValue(date4) {
-  return [(0, import_dayjs12.default)(date4).format("YYYY-MM-DD"), ...getTimePickerValue(date4)];
+function getDateTimePickerValue(date4, precision = "second") {
+  return [(0, import_dayjs12.default)(date4).format("YYYY-MM-DD"), ...getTimePickerValue(date4, precision)];
 }
-function applyDateTimePickerValue(base, value) {
+function applyDateTimePickerValue(base, value, precision = "second") {
   const [dateValue, hour, minute, second] = value;
   const date4 = (0, import_dayjs12.default)(String(dateValue || (0, import_dayjs12.default)(base).format("YYYY-MM-DD")));
-  return date4.hour(Number(hour ?? 0)).minute(Number(minute ?? 0)).second(Number(second ?? 0)).millisecond(0).toDate();
+  return date4.hour(Number(hour ?? 0)).minute(Number(minute ?? 0)).second(precision === "second" ? Number(second ?? 0) : 0).millisecond(0).toDate();
 }
 function MobileDateTimePickerView({
   value,
+  dateFormat,
   min: min2,
   max: max2,
   onChange
 }) {
+  const precision = resolveTimePickerPrecision(dateFormat);
   const columns = import_react216.default.useMemo(
-    () => [getDateOptions(value, min2, max2), hourOptions, minuteOptions, secondOptions],
-    [value, min2, max2]
+    () => [getDateOptions(value, min2, max2), ...getTimePickerColumns(precision)],
+    [value, min2, max2, precision]
   );
   return /* @__PURE__ */ (0, import_jsx_runtime34.jsx)(
     picker_view_default,
     {
       columns,
-      value: getDateTimePickerValue(value),
-      onChange: (nextValue) => onChange(applyDateTimePickerValue(value, nextValue)),
+      value: getDateTimePickerValue(value, precision),
+      onChange: (nextValue) => onChange(applyDateTimePickerValue(value, nextValue, precision)),
       className: "sy-mobile-time-picker sy-mobile-date-time-picker",
       renderLabel: (item) => item.label
     }
@@ -31873,10 +31884,10 @@ function DateFieldMobile({
             }
           ),
           mode === "time" ? /* @__PURE__ */ (0, import_jsx_runtime35.jsxs)(import_jsx_runtime35.Fragment, { children: [
-            /* @__PURE__ */ (0, import_jsx_runtime35.jsx)(MobileTimePickerView, { value: tempDate, onChange: setTempDate }),
+            /* @__PURE__ */ (0, import_jsx_runtime35.jsx)(MobileTimePickerView, { value: tempDate, dateFormat: format2, onChange: setTempDate }),
             /* @__PURE__ */ (0, import_jsx_runtime35.jsxs)("div", { className: "sy-mobile-date-time-footer", children: [
               /* @__PURE__ */ (0, import_jsx_runtime35.jsx)("span", { children: "\u9009\u62E9\u65F6\u95F4" }),
-              /* @__PURE__ */ (0, import_jsx_runtime35.jsx)("button", { type: "button", className: "sy-mobile-time-pill is-active", children: formatMobileTime(tempDate) })
+              /* @__PURE__ */ (0, import_jsx_runtime35.jsx)("button", { type: "button", className: "sy-mobile-time-pill is-active", children: formatMobileTime(tempDate, format2) })
             ] })
           ] }) : /* @__PURE__ */ (0, import_jsx_runtime35.jsxs)(import_jsx_runtime35.Fragment, { children: [
             /* @__PURE__ */ (0, import_jsx_runtime35.jsx)(
@@ -31907,7 +31918,7 @@ function DateFieldMobile({
                   type: "button",
                   className: "sy-mobile-time-pill",
                   onClick: () => setMode("time"),
-                  children: formatMobileTime(tempDate)
+                  children: formatMobileTime(tempDate, format2)
                 }
               )
             ] }) : null
@@ -32167,6 +32178,7 @@ function CascadeDateFieldMobile({
             MobileDateTimePickerView,
             {
               value: timeStep === "start" ? tempStart : tempEnd,
+              dateFormat: format2,
               min: timeStep === "start" ? min2 : endMin,
               max: max2,
               onChange: timeStep === "start" ? updateTempStart : updateTempEnd
@@ -46094,6 +46106,7 @@ var StandardFormPage = ({
   mode,
   initialValues,
   permissions,
+  api: externalApi,
   formUuid,
   appType,
   formInstanceId,
@@ -46107,7 +46120,7 @@ var StandardFormPage = ({
   const formType = normalizeStandardFormType(
     schema.template?.formType || (resolvedMode === "process" ? "process" : "form")
   );
-  const api = (0, import_react278.useMemo)(() => {
+  const submitApi = (0, import_react278.useMemo)(() => {
     if (!onSubmit) return void 0;
     return {
       submitFormData: async (payload) => onSubmit(
@@ -46120,6 +46133,13 @@ var StandardFormPage = ({
       }
     };
   }, [formType, onSubmit]);
+  const api = (0, import_react278.useMemo)(() => {
+    if (!externalApi && !submitApi) return void 0;
+    return {
+      ...externalApi ?? {},
+      ...submitApi ?? {}
+    };
+  }, [externalApi, submitApi]);
   if (resolvedMode === "process") {
     return /* @__PURE__ */ (0, import_jsx_runtime100.jsx)(
       ProcessDetailTemplate,