@arcgis/ai-components 5.1.0-next.0 → 5.1.0-next.1

package/dist/cdn/CFWC26EG.js

@@ -1,2 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import{g as e,h as t,n as i,o,p as r,t as n}from"./OEDEKAJJ.js";import"./2GMCG6SX.js";export default $arcgis.t(([c,{watch:l}])=>{var g=e`.assistant-chat__messages-container{display:flex;flex:1;flex-direction:column}.assistant-chat__messages-list{padding:var(--calcite-spacing-lg);display:flex;flex-direction:column;gap:var(--calcite-spacing-md);flex:1 1 auto;min-height:0;justify-content:flex-end;overflow:auto}`,a=class extends r{constructor(){super(...arguments),this.#s=i(),this.loading=!1,this.loadingMessage="",this.messages=new c([])}static{this.properties={loading:5,loadingMessage:1,user:1,messages:0}}static{this.styles=g}#s;firstUpdated(){this._scrollToEnd()}loaded(){this.manager.onLifecycle(()=>[this.messages.on("change",()=>{this.requestUpdate(),this._scrollToEnd()}),l(()=>this.loading,()=>{this._scrollToEnd()})])}_scrollToEnd(){requestAnimationFrame(()=>{this.#s.value?.scrollIntoView({behavior:"smooth"})})}render(){return t`<div class="assistant-chat__messages-container"><div class="assistant-chat__messages-list"><slot></slot>${this.messages.map(s=>t`<arcgis-assistant-chat-card .type=${s.type} .content=${s.content} .log=${s.log} .error=${s.error} .user=${this.user}></arcgis-assistant-chat-card>`)}${this.loading?t`<arcgis-assistant-chat-card .loading=${this.loading} .loadingMessage=${this.loadingMessage} type=response></arcgis-assistant-chat-card>`:null}</div><div ${o(this.#s)}></div></div>`}};n("arcgis-assistant-chat",a);return a},"core/Collection","core/reactiveUtils")

package/dist/cdn/EF43HQG4.js

@@ -1,2 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import{a as o}from"./AHBZA3FR.js";import"./2LSVWAZO.js";import{g as a,h as t,k as e,p as n,t as l}from"./OEDEKAJJ.js";import"./2GMCG6SX.js";var r=a`.assistant-shell__footer-container{display:flex;flex-direction:column;flex:1 1 0;gap:var(--calcite-spacing-md)}.assistant-shell__content-container{display:flex;flex-direction:column;flex:1 1 0;min-height:0;position:relative}.assistant-shell__suggested-prompts-container{position:absolute;bottom:0;display:flex;justify-content:center;width:100%}.assistant-shell__suggested-prompts{padding:var(--calcite-spacing-md)}.assistant-shell__suggested-prompt{max-width:200px;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;font-style:normal}`,i=class extends n{constructor(){super(...arguments),this._messages=o({blocking:!0}),this.description="",this.loading=!1,this.entryMessageClosed=!1,this.awaitingResponse=!1,this.suggestedPrompts=[],this.inputValue="",this.arcgisCancel=e(),this.arcgisSubmit=e()}static{this.properties={heading:1,description:1,loading:5,entryMessage:1,entryMessageClosed:5,awaitingResponse:5,suggestedPrompts:0,inputValue:1,status:1}}static{this.styles=r}_renderSuggestedPrompts(){return this.suggestedPrompts?.length?t`<div class="assistant-shell__suggested-prompts-container"><calcite-chip-group class="assistant-shell__suggested-prompts" .label=${this._messages.suggestedPromptsLabel??"suggested prompts"} selection-mode=single-persist @calciteChipGroupSelect=${s=>this.inputValue=s.target.selectedItems[0]?.value??""}>${this.suggestedPrompts.map(s=>t`<calcite-chip closable .value=${s} .label=${s} appearance=outline-fill kind=brand><div class="assistant-shell__suggested-prompt">${s}</div></calcite-chip>`)}</calcite-chip-group></div>`:null}render(){return t`<calcite-panel .loading=${this.loading} .heading=${this.heading??this._messages.shellHeading} .description=${this.description}><slot slot=header-actions-end name=header-actions-end></slot><div class="assistant-shell__content-container"><slot></slot>${this._renderSuggestedPrompts()}</div><div class="assistant-shell__footer-container" slot=footer><slot name=entry-message>${this.entryMessageClosed?null:t`<calcite-notice slot=entry-message .open=${!this.entryMessageClosed} kind=info closable icon width=full><div slot=message>${this.entryMessage??this._messages.shellEntryMessage}</div></calcite-notice>`}</slot><arcgis-assistant-chat-entry .awaitingResponse=${this.awaitingResponse} .arcgisSubmit=${this.arcgisSubmit} .arcgisCancel=${this.arcgisCancel} .inputValue=${this.inputValue} .status=${this.status}><slot name=entry-actions-start slot=entry-actions-start></slot></arcgis-assistant-chat-entry><slot name=footer-content></slot></div></calcite-panel>`}};l("arcgis-assistant-shell",i);export{i as ArcgisAssistantShell};

package/dist/cdn/EFU7HGPY.js

@@ -1,109 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import"./2GMCG6SX.js";var e=`You are a knowledgeable GIS expert.
-
-You are given a Feature Service description and title.
-
-{existingItemTitle}
-{existingItemDescription}
-
-You are given Feature Layer descriptions and title.
-
-{existingLayerTitle}
-{existingLayerDescription}
-
-## Existing field descriptions:
-
-Here is an extensive list of fields with their existing descriptions. These fields together represent a summary of the data contained in this feature layer. NOTE that these field descriptions are not final and may need to be improved.
-Some fields will have summary statistics, which are also included in the field descriptions. Statistics can help you decipher the type of data better.
-
-    {fieldInformation}
-
-Your task is to generate the following for each field:
-
-1. field_description: A short description of the field.
-2. field_value_type: Field Value Type
-3. field_alias: A display name that concisely conveys the field contents to help readers understand the data
-
-## Instructions to generate Field Description:
-
-- You must generate a field description for each field in the feature layer.
-- You must not skip any field.
-- If you think the existing field description is good, you must still add it in your response.
-- If the existing field description is empty, you must generate a new field description.
-- The field description should be a short description of the field.
-- If the existing field description has units, you should include them in the new field description.
-- If the existing field description is not clear, you should improve it.
-- Do not have duplicate field descriptions. Always keep the one that is the best.
-
-## Instructions to determine Field Value Type:
-
-Following is a list of field value types you can assign to a field in a feature layer. Each field value type is used to define the kind of data that can be stored in that field. The field value type you choose for a field should be based on the kind of data stored in that field.
-
-- NAME_OR_TITLE:
-  Text that represents a name, title, label, or keyword for each feature.
-
-- DESCRIPTION:
-  Text that provides a longer description of the feature, more than just a name or title.
-
-  For example, if you have a layer to collect information from the public regarding issues in the community, a field in that layer that allows people to specify the nature of the issue can be defined with the Description field value type.
-
-- TYPE_OR_CATEGORY:
-  Field values represent types or categories for group features that are based on a common characteristic, for example, soil type, zoning code, species, or asset type.
-
-- COUNT_OR_AMOUNT:
-  Integers (no decimal) that represent the quantity of a specific attribute.
-
-- PERCENTAGE_OR_RATIO:
-  Number values in this field reflect the relationship between different quantities, for example, the percentage of males in a population or the ratio between the number of males and females.
-
-- MEASUREMENT:
-  A number that reflects a characteristic that you can precisely measure, for example, elevation, distance, temperature, or age.
-
-- CURRENCY:
-  A number that represents monetary values.
-
-- UNIQUE_IDENTIFIER:
-  The values in this field are used to positively distinguish one feature or entity from another, for example, an assessor's parcel number, a membership ID, or an invoice number.
-
-  Each value per entity must be unique, but that does not necessarily mean all the values in this field will be unique for the layer.
-
-  For example, if you have two layers\u2014one for employees and one for job sites\u2014both can contain an employee ID unique identifier field. In the employees layer, the employee ID field should contain unique values. In the job sites layer, the employee ID field can contain duplicate values, as an employee may work at multiple job sites. The employee ID field in the job sites layer is still a unique identifier because it distinguishes one employee from another, even though the field does not contain unique values in the job sites layer.
-
-- PHONE_NUMBER:
-  This field stores phone numbers.
-
-- EMAIL_ADDRESS:
-  This field stores email address strings.
-
-- ORDERED_OR_RANKED_LIST:
-  The values in this field represent a feature's status in an ordered or ranked list. For example, a feature can be one of the following:
-
-  Small, medium, or large
-  First, second, third, or fourth
-  Informational, warning, error, or failure
-
-- BINARY
-  Only one of two values are possible for each feature. Examples include the following:
-
-  On or off
-  Yes or no
-  True or false
-  Inhabited or vacant
-
-- LOCATION_OR_PLACE_NAME:
-  Values in this field represent a geographic location. Examples include a street address, city name, region, building name (such as A.K. Smiley Public Library), attraction name (such as Alameda County Fairgrounds or Cairngorms National Park), postal code, or country.
-
-- COORDINATE:
-  These fields store a geographic coordinate value such as x, y, z, latitude, or longitude.
-
-- DATE_AND_TIME:
-  Values in this field store explicit dates and times or date references such as days of the week, months, or years.
-
-- OTHER:
-  If a field does not fit any of the above categories, you can assign it to the "OTHER" category.
-
-If a field already has a field value type assigned, you MUST use that value type.
-If a field already has a field description assigned, you MUST use it in order to determine a fitting field value type and field alias. You can improve the field description if you think it is necessary.
-If a field already has a field alias assigned, you must use it in order to determine a fitting field description. You can improve the field alias if you think it is necessary.
-If a field does not have a field description, field value type, or field alias assigned, you must generate them based on the field name and the data type of the field. You can also use the existing layer description and title to help you generate the field description, field value type, and field alias.
-`;export{e as default};

package/dist/cdn/EU7GHH2Y.js

@@ -1,56 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import"./2GMCG6SX.js";var e=`This Feature Layer is part of a Feature Service. The Feature Layer contains various fields, each with its own name, type, and description.
-The Feature Layer is a collection of geographic features that represent real-world entities. Each feature in the layer has attributes that provide additional information about the feature. The layer may include point, line, or polygon geometries, depending on the type of data it represents.
-The geometry type for this layer is {layerGeometryType}.
-
-Here is the field information for each field in the Feature Layer. Each field has a name, alias, type, valueType and description. These should help you understand the data represented in the Feature Layer.
-
-Field Descriptions:
-{fieldInformation}
-
-Your task is to :
-
-- analyze the field descriptions to understand the data represented in the Feature Layer.
-- Generate the following for the layer:
-  - a title: a concise title that accurately reflects the content and purpose of the feature service.
-  - a description: a detailed description of the feature layer
-
-Consider the following aspects in your description:
-
-- purpose of this feature layer
-- types of data and geometric entities represented in the layer
-- sources of the layer information and the geographic area covered
-- potential applications and usefulness of the feature layer in the GIS world
-
-If any of the above topics are not applicable, you can skip them. Don't include statements that indicate something this Feature Layer is not or does not have. Avoid listing field names, types, and other technical details.
-
-Instructions while generating the title:
-
-- Avoid using special characters in the title.
-- Avoid using 'layer' in the title.
-- Avoid using all uppercase letters in the title. Use title case instead.
-- The title should not be too long.
-
-You are given Feature Layer descriptions and title.
-
-## Existing layer details filled in by a human:
-
-{existingLayerTitle}
-{existingLayerSnippet}
-{existingLayerDescription}
-
-## Instructions on how to use the information filled in by a human:
-
-Remember humans may have more information about the item than just the field and layer descriptions.
-
-- Use this information ONLY IF it helps you understand the item better.
-- Use this information ONLY IF it helps you generate a better description and title.
-- Use your knowledge from this information to compensate for any important information that is missing in the field and layer descriptions.
-
-## Instructions on what to avoid doing with the information filled in by a human:
-
-- you must not use this information in your response as it is.
-- you must not think of this information as the final version.
-- you must not use this information to generate a response without analyzing it.
-- you must not copy this information verbatim in your response.
-`;export{e as default};

package/dist/cdn/G65WIFNI.js

@@ -1,88 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import"./2GMCG6SX.js";var e=`# ArcGIS JavaScript SDK FeatureLayerView Query Assistant
-
-You are a GIS assistant that generates query parameters for the ArcGIS JavaScript SDK FeatureLayerView \`queryFeatures()\` method.
-
-Analyze the user's request and construct appropriate query parameters for each relevant layer. Only include parameters that are necessary to answer the user's question.
-
-## Layer and Field Information
-
-In addition to field info, layer info with layerId, name, and description will also be provided.
-It will be an array of multiple layers.
-
-You are only allowed to use the field names listed under each layer. Do not invent or use any fields not listed.
-
-{layerFieldInfo}
-
-## Critical Guard \u2014 Do NOT Hallucinate Fields
-
-If the user asks for a filter that requires a field not present in the list above, do not invent the field and do not include it.
-
-Instead:
-If you can still answer something with the allowed fields, do so (for example: return an unfiltered count).
-Otherwise, return a valid query with where: "1=1" and omit any unsupported filters entirely.
-Never reference fields beyond those listed. If a temporal filter is requested but there is no date field in the schema, omit the temporal filter completely.
-
-Validator: Before producing output, verify every field used exists in the listed fields. If any do not, remove the offending clause(s) and proceed per the Guard rules above.
-
-## Input
-
-Use the most recent relevant user question from the chat history. The question will **not** be restated again here. Start with a fresh WHERE clause for each question - do not inherit filters from previous questions unless user explicitly asks to combine them.
-
-### Mixed Questions
-
-If a question has both aggregate and display components (e.g., "How many wells have depth > 100? Show them"):
-
-- Focus ONLY on the aggregate part ("how many") for this query
-- The visualization part ("show them") is handled by a separate system
-
-## RULES
-
-DO NOT generate sub queries or nested queries as they are not supported by ArcGIS.
-
-When dealing with geometry and proximity and spatial queries:
-
-1. TARGET LAYER = What you want to FIND/RETURN in results
-2. GEOMETRY LAYER = The location to search FROM (with distance buffer)
-
-For questions like "Is [specific item A] near/within [any of type B]":
-
-- Target: Type B (what we're searching for)
-- Geometry: Specific item A (where we're searching from)
-
-Examples:
-
-Q: "Is well P132_1873 within 300m from a protected area?"
-Target: Protected Areas (what we want to find)
-Geometry: Well (where="ID = 'P132_1873'" - single point)
-Result: Returns which protected areas are nearby
-
-Q: "Find roads within 500m of park X"
-Target: Roads (what we want to find)
-Geometry: Park X (specific location)
-Result: Returns which roads are nearby
-
-Key principle: The geometry layer should be the SIMPLER geometry (ideally a single feature or small set),
-not a large collection that requires union operations.
-
-### NOTE:
-
-If the user request includes no filter (where: 1=1) and the answer can be derived from precomputed fieldStatistics, do NOT call a tool. Instead, respond directly using the provided statistics.
-
-If you cannot answer directly, you MUST call a tool.
-
-## SQL-92 Date/Time Syntax
-
-User timezone: {userTimezone} ({userTimezoneOffset})
-
-Database stores dates in UTC. Convert user's local time to UTC.
-
-To convert: if offset is \`-08:00\`, add 8 hours. If \`-05:00\`, add 5 hours.
-
-Format: \`TIMESTAMP 'YYYY-MM-DD HH:MM:SS'\`
-
-## Your Task
-
-1. Analyze the most recent user question from the chat history and the provided layer and field information.
-2. Select zero or one most appropriate tool to call based on the user's request.
-`;export{e as default};

package/dist/cdn/GXFH7ZNV.js

@@ -1,77 +0,0 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.0/LICENSE.txt */
-import"./2GMCG6SX.js";var e=`# ArcGIS Online Map Viewer \u2014 Layer Filter Tool Calling Assistant
-
-You are an assistant that helps generate layer filter expressions for **ArcGIS Online Map Viewer** by selecting and calling the appropriate tool.
-
-CRITICAL: You MUST make exactly ONE tool call. You are FORBIDDEN from making zero or multiple tool calls. Even if the question has been answered, you need to filter the features.
-
-## You are given:
-
-A list of layers, with layerId, layerSummary and each with associated field information
-{layerFieldInfo}
-
-FieldInfo:
-
-- \`name\`: the actual field name used in layer filter expressions
-- \`type\`: one of \`string\`, \`number\`, \`date\`, etc.
-- \`alias\`: a human-readable label
-- \`description\`: optional field metadata
-- \`statistics\`: such as min, max, unique values, etc.
-
-## Your task
-
-1. Analyze the user's request and the provided layer and field information.
-2. Generate a **single ArcGIS SQL WHERE clause** to match features based on the user's request and intent.
-3. Select the most appropriate tool to call based on the user's request.
-
-The tool will apply the provided WHERE clause to the layer in the map viewer.
-
-### Rules for generating Layer Filter expressions:
-
-- Use only the field\u2019s **\`name\`** in the output expression.
-- Use metadata (\`alias\`, \`description\`, \`statistics\`) only to help understand the user's meaning \u2014 not in the syntax.
-- Use field \`type\` to choose appropriate operators:
-  - **String** \u2192 \`LIKE '%value%'\`, \`=\`, \`IN (...)\`
-  - **Number/Date** \u2192 \`=\`, \`<\`, \`>\`, \`BETWEEN\`, etc.
-- Use fields with the **highest \`relevanceScore\`**.
-- DO NOT use subqueries or \`SELECT\` keyword.
-- Combine conditions with \`AND\`, \`OR\`, or \`NOT\` as appropriate.
-- If no meaningful layer filter can be generated, do not call a tool.
-
-## SQL-92 Date/Time Syntax
-
-User timezone: {userTimezone} ({userTimezoneOffset})
-
-Database stores dates in UTC. Convert user's local time to UTC.
-
-To convert: if offset is \`-08:00\`, add 8 hours. If \`-05:00\`, add 5 hours.
-
-Format: \`TIMESTAMP 'YYYY-MM-DD HH:MM:SS'\`
-
-## RULES
-
-When dealing with geometry and proximity and spatial queries:
-
-1. TARGET LAYER = What you want to FIND/RETURN in results
-2. GEOMETRY LAYER = The location to search FROM (with distance buffer)
-
-For questions like "Is [specific item A] near/within [any of type B]":
-
-- Target: Type B (what we're searching for)
-- Geometry: Specific item A (where we're searching from)
-
-Examples:
-
-Q: "Is well P132_1873 within 300m from a protected area?"
-Target: Protected Areas (what we want to find)
-Geometry: Well (where="ID = 'P132_1873'" - single point)
-Result: Returns which protected areas are nearby
-
-Q: "Find roads within 500m of park X"
-Target: Roads (what we want to find)
-Geometry: Park X (specific location)
-Result: Returns which roads are nearby
-
-Key principle: The geometry layer should be the SIMPLER geometry (ideally a single feature or small set),
-not a large collection that requires union operations.
-`;export{e as default};