@uipath/packager-tool-bpmn 1.201.0-preview.115 → 1.201.0-preview.121

package/dist/bpmn-tool.d.ts

@@ -16,6 +16,74 @@ export declare class BpmnTool extends ProjectTool {
      * Copy all files from source path to content folder
      */
     private copyFiles;
+    /**
+     * Regenerate `entry-points.json` and `bindings_v2.json` in the staging
+     * content folder from the BPMN model.
+     *
+     * `package-descriptor.json` declares both files unconditionally, but they
+     * only reached the package if the project source already carried them —
+     * which depends on who authored it. A Studio Web `.uis` export omits both
+     * for ProcessOrchestration, so those packages were rejected by the Solution
+     * Feed every time (`1203`, or `1205` for the missing entry point) while
+     * `uip solution pack` still reported success (cli#3299).
+     *
+     * Regenerating unconditionally — rather than only filling gaps — matches
+     * `packager-tool-flow` and `uip maestro refresh`, and is safe here because
+     * entry-point identity is read from the BPMN and never minted:
+     * `<bpmn:startEvent id>` supplies the filePath fragment and
+     * `<uipath:entryPointId value>` the `uniqueId`. So a stale copy on disk
+     * cannot ship, and repacking the same source is idempotent. Author-owned
+     * detail survives: `buildBpmnPackageMetadata` merges existing JSON-schema
+     * annotations, and `buildConnectionResources` preserves resource entries it
+     * does not manage.
+     *
+     * Writes into `contentFolder` (the staging copy), never back into the
+     * user's project.
+     *
+     * Additive by design: when the model yields no entry point the project's own
+     * artifacts are left exactly as they were. `validateAsync` accepts a
+     * `<bpmn:startEvent>` without a `uipath:entryPointId` (a subprocess-only or
+     * event-triggered process is a legitimate shape), so deriving is an
+     * improvement where it is possible rather than a new gate — failing here
+     * would reject projects that pack today on something validation permits.
+     * Declining to derive is not the same as fabricating: an entry-point id is
+     * never minted, because a wrong one deploys clean and faults at run time.
+     */
+    private generateBpmnPackagingArtifacts;
+    /**
+     * Derive and write the artifacts. Returns `undefined` on success, or a
+     * human-readable reason why derivation was not possible — the caller decides
+     * whether that is fatal.
+     */
+    private deriveBpmnArtifacts;
+    /**
+     * Decide which BPMN model the artifacts are derived from.
+     *
+     * `project.uiproj` declares the answer in `MainFile`, so it decides. A
+     * directory listing must not: `readdir` order is filesystem-dependent, and
+     * a project may legitimately hold several models — a called subprocess, or a
+     * second process kept alongside the main one. Deriving from the wrong one
+     * mints entry points for a process nobody invokes, which publishes cleanly
+     * and then faults at run time, so an ambiguous project is declined instead
+     * of guessed.
+     *
+     * `MainFile` is absent from hand-authored and older projects, so a lone
+     * `.bpmn` file still resolves without it — that is unambiguous by itself.
+     *
+     * Returns the file name, or the reason no single model could be identified.
+     */
+    private selectBpmnFile;
+    /**
+     * `MainFile` from the staged `project.uiproj`, or `undefined` when the
+     * project does not declare one.
+     */
+    private readMainFile;
+    /**
+     * Read the artifacts already staged in content/, so regeneration can carry
+     * forward author-owned detail. Absent or unparseable files are treated as
+     * absent — the model is the source of truth.
+     */
+    private readExistingArtifacts;
     /**
      * Create operate.json file if it doesn't already exist
      */