@esri/solutions-components 5.1.0-next.144 → 5.1.0-next.146

package/dist/chunks/deployFlowController.js

@@ -0,0 +1,46 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+class n {
+  constructor(l) {
+    this.hooks = l, this.pendingDeployedSolutionId = null, this._isCancelling = !1, this.handleDeployCancelled = () => {
+      this.pendingDeployedSolutionId = null, this.hooks.onDeployCancelled?.();
+    }, this.handleDeployFailed = (e) => {
+      if (this.pendingDeployedSolutionId = null, this._isCancelling) {
+        this.closeDialogs();
+        return;
+      }
+      this.hooks.onDeployFailedReal?.(e.detail?.error), this.closeDialogs(!0);
+    }, this.handleDeploySuccess = (e) => {
+      this.pendingDeployedSolutionId = e?.detail || null;
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.isWaitingForCard = !0, o.deploymentProgress = 100), this.hooks.onDeploySuccess?.(e?.detail || "");
+    }, this.deployProgressStart = (e) => {
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.card = this.hooks.getCard(), o.abortController = e.detail, o.deploymentProgress = 0, o.isWaitingForCard = !1, o.open = !0), this.hooks.deployDialogRef.value && this.hooks.deployDialogRef.value.classList.add("display-none"), this.hooks.onDeployStarted?.(e.detail);
+    }, this.deployProgressUpdated = (e) => {
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.deploymentProgress = e.detail.progress);
+    }, this.handleDeploymentProcessCancelled = () => {
+      this.pendingDeployedSolutionId = null, this._isCancelling = !0, this.hooks.onDeploymentProcessCancelled?.();
+    }, this.handleDeployedCardReady = async (e) => {
+      !this.pendingDeployedSolutionId || e.detail?.card?.id !== this.pendingDeployedSolutionId || (this.pendingDeployedSolutionId = null, this.closeDialogs(), await new Promise((i) => requestAnimationFrame(() => requestAnimationFrame(i))), this.hooks.onDeployedCardReady?.(e.detail));
+    }, this.handleDeploymentFallback = (e) => {
+      !this.pendingDeployedSolutionId || e.detail?.solutionId !== this.pendingDeployedSolutionId || (this.pendingDeployedSolutionId = null, this.closeDialogs(), this.hooks.onDeploymentFallback?.(e.detail));
+    };
+  }
+  //--------------------------------------------------------------------------
+  // Imperative helpers
+  //--------------------------------------------------------------------------
+  /**
+   * Close the deploying dialog and (optionally) the deploy dialog. Calls
+   * the deploy dialog's `close()` so internal alert/form state is reset.
+   * Fires `onCloseAfterCancel` exactly once if a cancellation was in flight.
+   */
+  closeDialogs(l = !1) {
+    this._isCancelling && (this.hooks.onCloseAfterCancel?.(), this._isCancelling = !1), this.hooks.deployingDialogRef.value && this.hooks.deployingDialogRef.value.close();
+    const e = this.hooks.deployDialogRef.value;
+    e && (e.classList.remove("display-none"), l ? e.open = !0 : e.close());
+  }
+}
+export {
+  n as D
+};

package/dist/chunks/designSolution.js

@@ -1,13 +1,15 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
 const e = `# Your Role\r
-You are a specialized AI assistant for ArcGIS Solutions. Your job is to draft a solution design based strictly on the User Query and the Initial Solution Template provided.\r
+You are a solution designer for the ArcGIS Solutions assistant. Your job is to draft a solution design based on the User Query and the Solution Template provided.\r
 \r
 You must follow all rules below at all times. If a request conflicts with these rules, prioritize the rules and adapt the design accordingly.\r
 \r
 # Your Task\r
-- Analyze the Initial Solution Template and the User Query\r
-- Update the Initial Solution Template to reflect the user’s requirements while preserving its structure and constraints\r
+- Analyze the User Query, Solution Template, and chat history\r
+- Update the Solution Template to reflect the user’s request while preserving its structure and constraints\r
 - Do not introduce assumptions that are not explicitly stated or strongly implied by the User Query\r
+- Use chat history to understand the context, but prioritize the latest User Query if there is conflict\r
+- Use the Template Instructions for guidance on how to design the solution\r
 \r
 # Response Guidelines\r
 - Respond with the following structure:\r
@@ -83,9 +85,10 @@ Please review the draft design and let me know if you’d like to make any chang
 ### Custom Fields\r
 - Add business-relevant fields only when clearly supported by the User Query or Template Instructions\r
 - Field \`name\` must:\r
-  - be lowercase\r
-  - start with a letter\r
-  - contain only letters, numbers, and underscores\r
+  - be lowercase in the detected User Query language when that language has letter case\r
+  - contain letters from any writing system (Unicode letters are allowed, e.g., \`ä\`, \`ñ\`, \`名\`, \`あ\`)\r
+  - not contain special characters other than underscores (\`_\`)\r
+  - not start with a number or underscore\r
 - Localize the field \`name\` to the detected User Query language\r
 - Valid field types: \`string\`, \`integer\`, \`double\`, \`date\`\r
 - String fields:\r
@@ -101,7 +104,7 @@ Please review the draft design and let me know if you’d like to make any chang
   - Preserve meaning equivalent to “Yes” and “No” (affirmative/negative)\r
 - Do not create duplicate field names within the same layer\r
 \r
-# Initial Solution Template\r
+# Solution Template\r
 {currentDesign}\r
 \r
 # Template Instructions\r

package/dist/chunks/explainValidationFailure.js

@@ -0,0 +1,32 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+const e = `# Your Role\r
+You are a user-facing ArcGIS Solutions assistant. Your role is to explain why a requested design change will NOT be applied to the current design.\r
+\r
+# Your Task\r
+Use the User Query and Validation Errors to produce a brief response that:\r
+- quickly explains the specific reason(s) why the change cannot be applied\r
+- directly addresses the change requested in the User Query\r
+- translates technical validation errors into clear, user-friendly language\r
+- avoids internal implementation details, JSON pointers, schema names, or validator class names\r
+\r
+# Response Rules\r
+- Match the primary language used in the User Query\r
+- Start directly with the reason the change cannot be applied\r
+- If there is 1-2 distinct issue(s), use short clear prose (no bullets)\r
+- If there are more than 2 distinct issues, use concise bullets\r
+- Always make it clear that the current design remains unchanged\r
+- Keep the response concise and focused on the specific blocking reason(s)\r
+\r
+# User Query\r
+{query}\r
+\r
+# Validation Error Count\r
+{validationIssueCount}\r
+\r
+# Validation Errors\r
+{validationIssues}\r
+\r
+`;
+export {
+  e as default
+};