openxiangda 1.0.25 → 1.0.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -79,6 +79,7 @@ When the user provides a root domain such as `https://yida.wisejob.cn/`, use it
|
|
|
79
79
|
- If there is no `sy-lowcode-app-workspace`, create one with `openxiangda workspace init <dir>` before writing forms, pages, or JS_CODE nodes.
|
|
80
80
|
- Never treat `openxiangda form create` as page generation. It only creates a low-level platform form shell for diagnostics or for workspace publish internals. The source of user-facing pages is `sy-lowcode-app-workspace`.
|
|
81
81
|
- Publish normal form pages, workflow form pages, and custom code pages through `openxiangda workspace publish --profile <name>` from the app workspace.
|
|
82
|
+
- For live platform publishing, do not call `lowcode-workspace publish-all`, `pnpm publish:all`, or legacy project scripts such as `scripts/openxiangda-publish.mjs` directly. They are workspace internals and may miss the normal-user token/profile injection. Use `openxiangda workspace publish ...` so `OPENXIANGDA_PROFILE`, `OPENXIANGDA_BASE_URL`, `OPENXIANGDA_ACCESS_TOKEN`, and `OPENXIANGDA_APP_TYPE` are injected consistently.
|
|
82
83
|
- For routine AI edits, avoid reflexive full publish. First run `openxiangda workspace publish --profile <name> --changed --dry-run`, then use `--changed`, `--page <pageCode>`, `--form <formCode>`, or `--only pages/a,forms/b`. Use full publish only when broad shared/config changes intentionally affect many modules.
|
|
83
84
|
- 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.
|
|
84
85
|
- Use logical resource codes in local files. Platform-specific IDs such as `formUuid`, `pageId`, `workflowId`, and `automationId` must be isolated by profile.
|
|
@@ -6,6 +6,13 @@ Preferred publish command:
|
|
|
6
6
|
openxiangda workspace publish --profile <name>
|
|
7
7
|
```
|
|
8
8
|
|
|
9
|
+
Do not run `lowcode-workspace publish-all`, `pnpm publish:all`, or legacy
|
|
10
|
+
project scripts such as `scripts/openxiangda-publish.mjs` directly for live
|
|
11
|
+
publishing. Those commands are workspace internals. They may skip OpenXiangda's
|
|
12
|
+
normal-user token/profile injection and fall back to old `APP_KEY` /
|
|
13
|
+
`APP_SECRET` behavior, or publish with a buildId that the platform menu does not
|
|
14
|
+
activate. Use `openxiangda workspace publish ...` as the external entry.
|
|
15
|
+
|
|
9
16
|
For day-to-day AI edits, prefer a targeted publish:
|
|
10
17
|
|
|
11
18
|
```bash
|
|
@@ -154,6 +154,8 @@ openxiangda workspace publish --profile dev --only pages/dashboard,forms/custome
|
|
|
154
154
|
|
|
155
155
|
Do not run a full publish automatically after a single page or form edit. Full publish is for intentional broad changes, shared/config changes that affect many modules, or cache repair. Targeted publish skips resources by default; pass `--resources` or run `openxiangda resource publish` when resource manifests changed.
|
|
156
156
|
|
|
157
|
+
Do not call `lowcode-workspace publish-all`, `pnpm publish:all`, or legacy project scripts such as `scripts/openxiangda-publish.mjs` directly for live publishing. They are internal workspace commands and may not receive the normal-user access token from the selected profile. The external entry is always `openxiangda workspace publish ...`.
|
|
158
|
+
|
|
157
159
|
- `OPENXIANGDA_PROFILE`
|
|
158
160
|
- `OPENXIANGDA_BASE_URL`
|
|
159
161
|
- `OPENXIANGDA_ACCESS_TOKEN`
|