@arcgis/map-components 5.2.0-next.61 → 5.2.0-next.63

package/dist/components/arcgis-editor/customElement.d.ts

@@ -94,7 +94,7 @@ export abstract class ArcgisEditor extends LitElement {
    *
    * @default false
    * @internal
-   * @sine 5.1
+   * @since 5.1
    */
   accessor hideSelectionToolbar: boolean;
   /**
@@ -398,8 +398,8 @@ export abstract class ArcgisEditor extends LitElement {
    */
   accessor useLegacyCreateTools: boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-editor component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-editor component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /**

package/dist/components/arcgis-elevation-profile/customElement.d.ts

@@ -499,8 +499,8 @@ export abstract class ArcgisElevationProfile extends LitElement {
    */
   accessor uniformChartScaling: boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-elevation-profile component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-elevation-profile component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**

package/dist/components/arcgis-expand/customElement.d.ts

@@ -198,8 +198,8 @@ export abstract class ArcgisExpand extends LitElement {
    */
   accessor topLayerDisabled: boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-expand component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-expand component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapView | SceneView | null | undefined;
   /**

package/dist/components/arcgis-feature/customElement.d.ts

@@ -395,8 +395,8 @@ export abstract class ArcgisFeature extends LitElement {
    */
   accessor timeZone: string;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /**

package/dist/components/arcgis-feature-next/customElement.d.ts

@@ -361,8 +361,8 @@ export abstract class ArcgisFeatureNext extends LitElement {
    */
   accessor timeZone: string;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-next component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-next component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-feature-next/customElement.js

@@ -13,7 +13,7 @@ import { a as R, g as D, c as V, b as k, s as d, i as E, d as B } from "../../ch
 import N from "@arcgis/core/core/Collection.js";
 import { watch as H } from "@arcgis/core/core/reactiveUtils.js";
 import { stripHTML as P } from "@arcgis/core/applications/Components/stringUtils.js";
-import Z from "@arcgis/core/popup/Feature.js";
+import Z from "@arcgis/core/popup/FeatureContent.js";
 const z = w`:host{display:flex;flex:1 1 auto;background-color:var(--calcite-color-foreground-1);--calcite-color-background: var(--calcite-color-foreground-1)}.root{flex:1 1 auto}.root calcite-icon{box-sizing:content-box}.loading-container{display:flex;justify-content:center;padding:var(--calcite-spacing-md) 0;width:100%}.content-element{margin-bottom:var(--calcite-spacing-lg);padding:0 var(--calcite-spacing-sm);display:flex;flex-direction:column}.content-element:only-child,.content-element:last-child{margin-bottom:var(--calcite-spacing-xxs)}.last-edited-info{padding-top:var(--calcite-spacing-xs);font-size:var(--calcite-font-size-sm)}`, U = C(Z);
 class S extends b {
   constructor() {

package/dist/components/arcgis-feature-relationship/customElement.js

@@ -14,7 +14,7 @@ import M from "@arcgis/core/rest/support/RelationshipQuery.js";
 import { ignoreAbortErrors as L } from "@arcgis/core/core/promiseUtils.js";
 import { classes as S } from "@arcgis/toolkit/dom";
 import { createRef as J, ref as U } from "lit/directives/ref.js";
-import X from "@arcgis/core/popup/Feature.js";
+import X from "@arcgis/core/popup/FeatureContent.js";
 const Y = H`:host{position:relative;flex:1 1 auto}.list{min-height:var(--calcite-spacing-xxxl)}.list-item-hidden{display:none}.feature-observer{position:relative;bottom:var(--calcite-spacing-xxl);z-index:2;text-align:center}.sticky-loading-container{display:flex;position:sticky;bottom:var(--calcite-spacing-sm);align-items:center;justify-content:center;z-index:2;margin:0;padding:0;height:var(--calcite-spacing-xxxl);pointer-events:none}`, ee = (h) => {
   const e = [];
   if (h.formTemplate) {

package/dist/components/arcgis-feature-table/customElement.d.ts

@@ -1074,8 +1074,8 @@ export abstract class ArcgisFeatureTable extends LitElement {
    */
   accessor timeZone: string | null | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-table component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-table component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapViewOrSceneView | null | undefined;
   /**

package/dist/components/arcgis-feature-templates/customElement.d.ts

@@ -243,8 +243,8 @@ export abstract class ArcgisFeatureTemplates extends LitElement {
    */
   get updating(): boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-templates component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-feature-templates component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /** Permanently destroy the component */

package/dist/components/arcgis-feature-utility-network-associations/customElement.js

@@ -13,7 +13,7 @@ import P from "@arcgis/core/rest/networks/support/NetworkElement.js";
 import U from "@arcgis/core/rest/networks/support/QueryAssociationsParameters.js";
 import { LitElement as Q, renderElement as q } from "@arcgis/lumina";
 import { debounce as T } from "@arcgis/toolkit/function";
-import G from "@arcgis/core/popup/Feature.js";
+import G from "@arcgis/core/popup/FeatureContent.js";
 const B = M`.list-container{min-height:var(--calcite-spacing-xxxl)}.loading-container{display:flex;justify-content:center;padding:var(--calcite-spacing-md) 0;width:100%}.sticky-loading-container{display:flex;position:sticky;bottom:var(--calcite-spacing-sm);align-items:center;justify-content:center;z-index:2;margin:0;padding:0;height:var(--calcite-spacing-xxxl);pointer-events:none;height:500px}`, L = 100, $ = {
   assetGroup: "assetgroup",
   assetType: "assettype"

package/dist/components/arcgis-features-next/customElement.d.ts

@@ -54,7 +54,7 @@ export abstract class ArcgisFeaturesNext extends LitElement {
    */
   accessor actions: Collection<PopupAction>;
   /**
-   * Indicates if the component is active when it is visible and is not [waiting](https://developers.arcgis.com/javascript/latest/references/core/popup/Features/#waitingForResult) for results.
+   * Indicates if the component is active when it is visible and is not [waiting](https://developers.arcgis.com/javascript/latest/references/core/popup/FeatureContentCollection/#waitingForResult) for results.
    *
    * @default false
    */

package/dist/components/arcgis-features-next/customElement.js

@@ -4,7 +4,7 @@ import { css as O, html as o } from "lit";
 import { keyed as y } from "lit/directives/keyed.js";
 import R from "@arcgis/core/support/actions/ActionButton.js";
 import E from "@arcgis/core/core/Collection.js";
-import H from "@arcgis/core/popup/Features.js";
+import H from "@arcgis/core/popup/FeatureContentCollection.js";
 import { LitElement as P, createEvent as A, renderElement as z, nothing as p, safeClassMap as I } from "@arcgis/lumina";
 import { useDirection as Z, usePropertyChange as V, bypassReadOnly as k } from "@arcgis/lumina/controllers";
 import { classes as x } from "@arcgis/toolkit/dom";

package/dist/components/arcgis-floor-filter/customElement.d.ts

@@ -191,8 +191,8 @@ export abstract class ArcgisFloorFilter extends LitElement {
   /** The currently selected site. */
   accessor site: string | null | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-floor-filter component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-floor-filter component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-grid-controls/customElement.d.ts

@@ -319,8 +319,8 @@ export abstract class ArcgisGridControls extends LitElement {
    */
   accessor unit: LengthUnit | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-grid-controls component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-grid-controls component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-home/customElement.d.ts

@@ -89,8 +89,8 @@ export abstract class ArcgisHome extends LitElement {
   /** The current state of the component. */
   get state(): "disabled" | "going-home" | "ready";
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-home component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-home component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**

package/dist/components/arcgis-layer-list/customElement.d.ts

@@ -403,8 +403,8 @@ export abstract class ArcgisLayerList extends LitElement {
   /** The TableList that displays the tables associated with a KnowledgeGraphLayer. */
   get tableList(): TableList | null | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-layer-list component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-layer-list component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /**

package/dist/components/arcgis-layer-list-next/customElement.d.ts

@@ -206,6 +206,20 @@ export abstract class ArcgisLayerListNext extends LitElement {
    * @default false
    */
   accessor hideCatalogLayerList: boolean;
+  /**
+   * This property provides the ability to show or hide the no items to display notice when there are no filter results.
+   *
+   * @default false
+   * @since 5.2
+   */
+  accessor hideNoFilterResultsNotice: boolean;
+  /**
+   * This property provides the ability to show or hide the no items to display notice.
+   *
+   * @default false
+   * @since 5.2
+   */
+  accessor hideNoItemsNotice: boolean;
   /**
    * This property provides the ability to show or hide status indicators.
    *
@@ -554,8 +568,8 @@ export abstract class ArcgisLayerListNext extends LitElement {
    */
   get tableList(): ArcgisTableListNext | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-layer-list-next component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-layer-list-next component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /**

package/dist/components/arcgis-layer-list-next/customElement.js

@@ -2,15 +2,15 @@
 import { c as R } from "../../chunks/runtime.js";
 import { html as h } from "lit";
 import { keyed as v } from "lit/directives/keyed.js";
-import { repeat as x } from "lit/directives/repeat.js";
-import B from "@arcgis/core/widgets/LayerList/LayerListViewModel.js";
-import { classes as k } from "@arcgis/toolkit/dom";
-import { generateGuid as S } from "@arcgis/toolkit/string";
+import { repeat as N } from "lit/directives/repeat.js";
+import x from "@arcgis/core/widgets/LayerList/LayerListViewModel.js";
+import { classes as B } from "@arcgis/toolkit/dom";
+import { generateGuid as k } from "@arcgis/toolkit/string";
 import { createRef as w, ref as b } from "lit/directives/ref.js";
-import { u as U } from "../../chunks/useT9n.js";
-import { m as N } from "../../chunks/useViewModel.js";
+import { u as S } from "../../chunks/useT9n.js";
+import { m as U } from "../../chunks/useViewModel.js";
 import { g as $ } from "../../chunks/globalCss.js";
-import { c as f } from "../../chunks/css.js";
+import { c as y } from "../../chunks/css.js";
 import { g as d, a as F, m as G, b as H, r as V, s as j, c as q, d as z, e as J } from "../../chunks/layer-list-utils.js";
 import m from "@arcgis/core/core/Collection.js";
 import { on as C, watch as K } from "@arcgis/core/core/reactiveUtils.js";
@@ -22,19 +22,19 @@ import { u as Y } from "../../chunks/useCloseEvent.js";
 import { ArcgisLayerListItem as Z } from "./layer-list-item/customElement.js";
 import { s as ee, a as te } from "../../chunks/layer-list-next.js";
 import "../arcgis-layer-list-item-indicator/customElement.js";
-const O = "nested", se = N(B);
+const O = "nested", se = U(x);
 class ie extends Q {
   constructor() {
-    super(...arguments), this._lastDragDetail = null, this._rootListRef = w(), this._layerFlowItemRef = w(), this._panelFlowItemRef = w(), this._selectedDragItemLayerUid = null, this._rootGroupUid = `operational-${S()}`, this._openedLayersController = null, this.messages = U(), this._canMove = ({ dragEl: e, fromEl: t, toEl: s }, a) => {
+    super(...arguments), this._lastDragDetail = null, this._rootListRef = w(), this._layerFlowItemRef = w(), this._panelFlowItemRef = w(), this._selectedDragItemLayerUid = null, this._rootGroupUid = `operational-${k()}`, this._openedLayersController = null, this.messages = S(), this._canMove = ({ dragEl: e, fromEl: t, toEl: s }, a) => {
       const i = a === "pull" ? this.listItemCanGiveFunction : this.listItemCanReceiveFunction, r = d(e, this.operationalItems);
       if (!r?.sortable)
         return !1;
-      const o = this._resolveListContainer(t), l = this._resolveListContainer(s), n = this._getContainerItem(o), p = F(o), g = this._getContainerItem(l), u = F(l), I = !!p && !!u && p === u, y = {
+      const o = this._resolveListContainer(t), l = this._resolveListContainer(s), n = this._getContainerItem(o), p = F(o), g = this._getContainerItem(l), u = F(l), I = !!p && !!u && p === u, f = {
         selected: r,
         from: n,
         to: g
       }, _ = o?.group, c = l?.group, P = n?.layer?.type ?? "", D = g?.layer?.type ?? "", T = /* @__PURE__ */ new Set(["map-image", "catalog", "knowledge-graph"]);
-      return _ && c && typeof i == "function" ? i(y) : I && !T.has(P) && !T.has(D) && r?.layer?.type !== "sublayer";
+      return _ && c && typeof i == "function" ? i(f) : I && !T.has(P) && !T.has(D) && r?.layer?.type !== "sublayer";
     }, this._onCatalogOpen = (e) => {
       this.openedLayers.push(e.layer?.parent);
     }, this._onTablesOpen = (e) => {
@@ -46,7 +46,7 @@ class ie extends Q {
     }, this._setActiveItem = (e) => {
       if (this.visibilityAppearance !== "default")
         return;
-      const t = Array.from(e.composedPath()).find((a) => a.classList?.contains(f.item)), s = d(t, this.operationalItems);
+      const t = Array.from(e.composedPath()).find((a) => a.classList?.contains(y.item)), s = d(t, this.operationalItems);
       this._activeItem = s;
     }, this.viewModel = se(this), this.arcgisClose = Y(this), this._activeItem = null, this._onTooltipReferenceChange = (e, t) => {
       t ? this._tooltipReferenceMap.set(e, t) : this._tooltipReferenceMap.delete(e);
@@ -54,10 +54,10 @@ class ie extends Q {
       this._selectedDragItemLayerUid = e;
     }, this._onTriggerAction = (e, t) => {
       this.triggerAction(e, t);
-    }, this._tooltipReferenceMap = /* @__PURE__ */ new Map(), this._layerListMap = /* @__PURE__ */ new Map(), this.layerTablesEnabled = new m(["knowledge-graph"]), this.mapImageOptions = null, this.openedLayerLists = new m(), this.tileOptions = null, this.view = this.viewModel.view, this.autoDestroyDisabled = !1, this.closed = !1, this.icon = "layers", this.collapsed = !1, this.dragEnabled = !1, this.filterPlaceholder = "", this.filterText = "", this.headingLevel = 2, this.layerTablesAvailable = new m(["knowledge-graph"]), this.listItemCreatedFunction = this.viewModel.listItemCreatedFunction, this.minDragEnabledItems = G, this.minFilterItems = H, this.openedLayers = new m(), this.operationalItems = this.viewModel.operationalItems, this.selectedItems = new m(), this.selectionMode = "none", this.visibilityAppearance = "default", this.hideCatalogLayerList = !1, this.showCloseButton = !1, this.showCollapseButton = !1, this.showErrors = !1, this.showFilter = !1, this.showHeading = !1, this.hideStatusIndicators = !1, this.showTemporaryLayerIndicators = !1, this.state = this.viewModel.state, this.arcgisPropertyChange = W()("state"), this.arcgisReady = L(), this.arcgisFilterChange = L(), this.arcgisSelectedItemsChange = L(), this.arcgisOpenedLayersChange = L(), this.arcgisTriggerAction = X(() => this.viewModel, "trigger-action");
+    }, this._tooltipReferenceMap = /* @__PURE__ */ new Map(), this._layerListMap = /* @__PURE__ */ new Map(), this.layerTablesEnabled = new m(["knowledge-graph"]), this.mapImageOptions = null, this.openedLayerLists = new m(), this.tileOptions = null, this.view = this.viewModel.view, this.autoDestroyDisabled = !1, this.closed = !1, this.icon = "layers", this.collapsed = !1, this.dragEnabled = !1, this.filterPlaceholder = "", this.filterText = "", this.headingLevel = 2, this.layerTablesAvailable = new m(["knowledge-graph"]), this.listItemCreatedFunction = this.viewModel.listItemCreatedFunction, this.minDragEnabledItems = G, this.minFilterItems = H, this.openedLayers = new m(), this.operationalItems = this.viewModel.operationalItems, this.selectedItems = new m(), this.selectionMode = "none", this.visibilityAppearance = "default", this.hideCatalogLayerList = !1, this.showCloseButton = !1, this.showCollapseButton = !1, this.showErrors = !1, this.hideNoFilterResultsNotice = !1, this.hideNoItemsNotice = !1, this.showFilter = !1, this.showHeading = !1, this.hideStatusIndicators = !1, this.showTemporaryLayerIndicators = !1, this.state = this.viewModel.state, this.arcgisPropertyChange = W()("state"), this.arcgisReady = L(), this.arcgisFilterChange = L(), this.arcgisSelectedItemsChange = L(), this.arcgisOpenedLayersChange = L(), this.arcgisTriggerAction = X(() => this.viewModel, "trigger-action");
   }
   static {
-    this.properties = { _catalogLayerList: 16, _tableList: 16, _tooltipReferenceMap: 16, _layerListMap: 16, _totalItems: 16, _visibleItems: 16, _openedPanelItems: 16, _dragEnabled: 16, _filterEnabled: 16, layerTablesEnabled: 16, mapImageOptions: 16, openedLayerLists: 16, tileOptions: 16, _renderedOpenLayerFlowItems: 16, view: 0, autoDestroyDisabled: 5, closed: 5, referenceElement: 1, icon: 1, catalogLayerList: 32, catalogOptions: 0, collapsed: 5, dragEnabled: 5, filterPlaceholder: 1, filterPredicate: 0, filterText: 1, headingLevel: 9, knowledgeGraphOptions: 0, layerTablesAvailable: 0, listItemCanGiveFunction: 0, listItemCanReceiveFunction: 0, listItemCreatedFunction: 0, minDragEnabledItems: 9, minFilterItems: 9, openedLayers: 32, operationalItems: 0, selectedItems: 0, selectionMode: 1, tableList: 32, visibilityAppearance: 1, hideCatalogLayerList: 5, showCloseButton: 5, showCollapseButton: 5, showErrors: 5, showFilter: 5, showHeading: 5, hideStatusIndicators: 5, showTemporaryLayerIndicators: 5, messageOverrides: 0, label: 1, state: 32 };
+    this.properties = { _catalogLayerList: 16, _tableList: 16, _tooltipReferenceMap: 16, _layerListMap: 16, _totalItems: 16, _visibleItems: 16, _openedPanelItems: 16, _dragEnabled: 16, _filterEnabled: 16, layerTablesEnabled: 16, mapImageOptions: 16, openedLayerLists: 16, tileOptions: 16, _renderedOpenLayerFlowItems: 16, view: 0, autoDestroyDisabled: 5, closed: 5, referenceElement: 1, icon: 1, catalogLayerList: 32, catalogOptions: 0, collapsed: 5, dragEnabled: 5, filterPlaceholder: 1, filterPredicate: 0, filterText: 1, headingLevel: 9, knowledgeGraphOptions: 0, layerTablesAvailable: 0, listItemCanGiveFunction: 0, listItemCanReceiveFunction: 0, listItemCreatedFunction: 0, minDragEnabledItems: 9, minFilterItems: 9, openedLayers: 32, operationalItems: 0, selectedItems: 0, selectionMode: 1, tableList: 32, visibilityAppearance: 1, hideCatalogLayerList: 5, showCloseButton: 5, showCollapseButton: 5, showErrors: 5, hideNoFilterResultsNotice: 5, hideNoItemsNotice: 5, showFilter: 5, showHeading: 5, hideStatusIndicators: 5, showTemporaryLayerIndicators: 5, messageOverrides: 0, label: 1, state: 32 };
   }
   static {
     this.styles = [ee, te];
@@ -236,7 +236,7 @@ class ie extends Q {
       [$.hidden]: e === "loading",
       [$.disabled]: e === "disabled"
     };
-    return h`<div class=${E(k($.widget, t))}>${this._visibleItems?.length ? this._renderItemTooltips() : null}${this._renderItems()}</div>`;
+    return h`<div class=${E(B($.widget, t))}>${this._visibleItems?.length ? this._renderItemTooltips() : null}${this._renderItems()}</div>`;
   }
   _renderItemTooltip(e) {
     const { _tooltipReferenceMap: t, messages: s } = this;
@@ -255,7 +255,7 @@ class ie extends Q {
     return h`<div slot=message>${this.messages.noItemsToDisplay}</div>`;
   }
   _renderNoItems() {
-    return h`<div class=${E(f.itemMessage)}><calcite-notice icon=information kind=info open width=full>${this._renderNoItemsMessage()}</calcite-notice></div>`;
+    return this.hideNoItemsNotice ? null : h`<div class=${E(y.itemMessage)}><calcite-notice icon=information kind=info open width=full>${this._renderNoItemsMessage()}</calcite-notice></div>`;
   }
   _renderLayerFlowItem(e, t) {
     const { messages: s, openedLayers: a } = this, i = e.title || this.messages.untitledLayer;
@@ -265,7 +265,7 @@ class ie extends Q {
   }
   _renderPanelFlowItems() {
     const { _openedPanelItems: e, openedLayers: t } = this;
-    return x(e.toArray(), (a) => a.uid, (a, i) => {
+    return N(e.toArray(), (a) => a.uid, (a, i) => {
       const { panel: r, title: o } = a, l = () => this._handlePanelFlowItemBack(r);
       return h`<calcite-flow-item .description=${o} .heading=${r.title} .headingLevel=${this.headingLevel} .selected=${!t.length && i === e.length - 1} @calciteFlowItemBack=${(n) => {
         n.preventDefault(), l();
@@ -273,17 +273,17 @@ class ie extends Q {
     });
   }
   _renderItems() {
-    const { collapsed: e, _visibleItems: t, _openedPanelItems: s, _filterEnabled: a, _rootGroupUid: i, showCloseButton: r, showCollapseButton: o, showHeading: l, _dragEnabled: n, selectionMode: p, filterText: g, openedLayers: u, filterPlaceholder: I, messages: y } = this, _ = [
-      h`<calcite-flow-item .closable=${r} .closed=${this.closed} .collapsed=${e} .collapsible=${o} .heading=${l ? y.componentLabel : void 0} .headingLevel=${this.headingLevel} .selected=${!u.length && !s.length} @calciteFlowItemClose=${() => this.closed = !1}>${t?.length ? h`<calcite-list @focusin=${this._setActiveItem} @focusout=${this._clearActiveItem} .canPull=${(c) => this._canMove(c, "pull")} .canPut=${(c) => this._canMove(c, "put")} data-layer-type=${i ?? A} .displayMode=${O} .dragEnabled=${n} .filterEnabled=${a} .filterPlaceholder=${I} .filterProps=${J} .filterText=${a ? g : ""} .group=${i} .label=${y.componentLabel} @mouseleave=${this._clearActiveItem} @mouseover=${this._setActiveItem} selection-appearance=highlight .selectionMode=${p} @calciteListChange=${this._handleCalciteListChange} @calciteListFilter=${(c) => {
+    const { collapsed: e, _visibleItems: t, _openedPanelItems: s, _filterEnabled: a, _rootGroupUid: i, showCloseButton: r, showCollapseButton: o, showHeading: l, _dragEnabled: n, selectionMode: p, filterText: g, openedLayers: u, filterPlaceholder: I, messages: f } = this, _ = [
+      h`<calcite-flow-item .closable=${r} .closed=${this.closed} .collapsed=${e} .collapsible=${o} .heading=${l ? f.componentLabel : void 0} .headingLevel=${this.headingLevel} .selected=${!u.length && !s.length} @calciteFlowItemClose=${() => this.closed = !1}>${t?.length ? h`<calcite-list @focusin=${this._setActiveItem} @focusout=${this._clearActiveItem} .canPull=${(c) => this._canMove(c, "pull")} .canPut=${(c) => this._canMove(c, "put")} data-layer-type=${i ?? A} .displayMode=${O} .dragEnabled=${n} .filterEnabled=${a} .filterPlaceholder=${I} .filterProps=${J} .filterText=${a ? g : ""} .group=${i} .label=${f.componentLabel} @mouseleave=${this._clearActiveItem} @mouseover=${this._setActiveItem} selection-appearance=highlight .selectionMode=${p} @calciteListChange=${this._handleCalciteListChange} @calciteListFilter=${(c) => {
         this.filterText = c.currentTarget?.filterText ?? "", this.arcgisFilterChange.emit();
-      }} @calciteListOrderChange=${(c) => this._onCalciteListOrderChange(c.detail)} @calciteListDragEnd=${(c) => this._onCalciteListDragEnd(c.detail)} ${b(this._rootListRef)}>${t.toArray().map((c) => this._renderItem(c))}${a ? h`<div class=${E(f.filterNoResults)} slot=filter-no-results><calcite-notice kind=info open width=full>${this._renderNoItemsMessage()}</calcite-notice></div>` : null}</calcite-list>` : this._renderNoItems()}</calcite-flow-item>`,
+      }} @calciteListOrderChange=${(c) => this._onCalciteListOrderChange(c.detail)} @calciteListDragEnd=${(c) => this._onCalciteListDragEnd(c.detail)} ${b(this._rootListRef)}>${t.toArray().map((c) => this._renderItem(c))}${a && !this.hideNoFilterResultsNotice ? h`<div class=${E(y.filterNoResults)} slot=filter-no-results><calcite-notice kind=info open width=full>${this._renderNoItemsMessage()}</calcite-notice></div>` : null}</calcite-list>` : this._renderNoItems()}</calcite-flow-item>`,
       this._renderPanelFlowItems(),
       this._renderedOpenLayerFlowItems
     ];
     return this.closed ? null : v("root-flow", h`<calcite-flow>${_}</calcite-flow>`);
   }
   _renderItem(e, t, s) {
-    return v(e.uid, Z({ activeItem: this._activeItem, canMove: this._canMove, css: f, displayMode: O, dragEnabled: this.dragEnabled, hideStatusIndicators: this.hideStatusIndicators, hideCatalogLayerList: this.hideCatalogLayerList, item: e, messages: this.messages, layerTablesEnabled: this.layerTablesEnabled, listModeDisabled: this.viewModel.listModeDisabled, operationalItems: this.operationalItems, parent: t, parentTitles: s, rootGroupUid: this._rootGroupUid, selectedDragItemLayerUid: this._selectedDragItemLayerUid, selectedItems: this.selectedItems, selectionMode: this.selectionMode, setCurrentActiveItem: this._setCurrentActiveItem, showTemporaryLayerIndicators: this.showTemporaryLayerIndicators, showCloseButton: this.showCloseButton, showCollapseButton: this.showCollapseButton, showErrors: this.showErrors, showHeading: this.showHeading, showFilter: this.showFilter, clearActiveItem: this._clearActiveItem, visibilityAppearance: this.visibilityAppearance, handleAction: this._onTriggerAction, handleCatalogOpen: this._onCatalogOpen, handleSelectedDragItemLayerUidChange: this._onSelectedDragItemLayerUidChange, handleTablesOpen: this._onTablesOpen, handleTooltipReferenceChange: this._onTooltipReferenceChange, view: this.view }));
+    return v(e.uid, Z({ activeItem: this._activeItem, canMove: this._canMove, css: y, displayMode: O, dragEnabled: this.dragEnabled, hideStatusIndicators: this.hideStatusIndicators, hideCatalogLayerList: this.hideCatalogLayerList, item: e, messages: this.messages, layerTablesEnabled: this.layerTablesEnabled, listModeDisabled: this.viewModel.listModeDisabled, operationalItems: this.operationalItems, parent: t, parentTitles: s, rootGroupUid: this._rootGroupUid, selectedDragItemLayerUid: this._selectedDragItemLayerUid, selectedItems: this.selectedItems, selectionMode: this.selectionMode, setCurrentActiveItem: this._setCurrentActiveItem, showTemporaryLayerIndicators: this.showTemporaryLayerIndicators, showCloseButton: this.showCloseButton, showCollapseButton: this.showCollapseButton, showErrors: this.showErrors, showHeading: this.showHeading, showFilter: this.showFilter, clearActiveItem: this._clearActiveItem, visibilityAppearance: this.visibilityAppearance, handleAction: this._onTriggerAction, handleCatalogOpen: this._onCatalogOpen, handleSelectedDragItemLayerUidChange: this._onSelectedDragItemLayerUidChange, handleTablesOpen: this._onTablesOpen, handleTooltipReferenceChange: this._onTooltipReferenceChange, view: this.view }));
   }
 }
 R("arcgis-layer-list-next", ie);

package/dist/components/arcgis-legend/customElement.d.ts

@@ -439,8 +439,8 @@ export abstract class ArcgisLegend extends LitElement {
    */
   get state(): LegendViewModelState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-legend component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-legend component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapViewOrSceneView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-line-of-sight/customElement.d.ts

@@ -201,8 +201,8 @@ export abstract class ArcgisLineOfSight extends LitElement {
    */
   get state(): "created" | "creating" | "disabled" | "ready";
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-line-of-sight component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-line-of-sight component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /** Clear the current analysis results. After calling this method, the user can set a new observer and targets. */

package/dist/components/arcgis-link-chart-layout-switcher/customElement.d.ts

@@ -131,8 +131,8 @@ export abstract class ArcgisLinkChartLayoutSwitcher extends LitElement {
    */
   get state(): LinkChartLayoutSwitcherViewModelState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-link-chart-layout-switcher component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-link-chart-layout-switcher component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-link-chart-nonspatial-visibility-toggle/customElement.d.ts

@@ -48,8 +48,8 @@ export abstract class ArcgisLinkChartNonspatialVisibilityToggle extends LitEleme
    */
   get state(): State;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-link-chart-nonspatial-visibility-toggle component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-link-chart-nonspatial-visibility-toggle component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | undefined;
   /**

package/dist/components/arcgis-locate/customElement.d.ts

@@ -145,8 +145,8 @@ export abstract class ArcgisLocate extends LitElement {
   /** The current state of the component. */
   get state(): State;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-locate component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-locate component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**

package/dist/components/arcgis-measurement/customElement.d.ts

@@ -165,8 +165,8 @@ export abstract class ArcgisMeasurement extends LitElement {
    */
   get state(): MeasurementState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-measurement component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-measurement component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapViewOrSceneView | null | undefined;
   /** Removes all measurement widgets and associated graphics. */

package/dist/components/arcgis-multi-feature-form/customElement.d.ts

@@ -76,8 +76,8 @@ export abstract class ArcgisMultiFeatureForm extends LitElement {
   /** @default false */
   get valid(): boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-multi-feature-form component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-multi-feature-form component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-navigation-toggle/customElement.d.ts

@@ -84,8 +84,8 @@ export abstract class ArcgisNavigationToggle extends LitElement {
   /** The current state of the component. */
   get state(): NavigationToggleState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-navigation-toggle component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-navigation-toggle component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /**

package/dist/components/arcgis-oriented-imagery-viewer/customElement.d.ts

@@ -193,8 +193,8 @@ export abstract class ArcgisOrientedImageryViewer extends LitElement {
    */
   get referencePoint(): Point | null;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-oriented-imagery-viewer component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-oriented-imagery-viewer component will be associated with a map or scene component rather than using the `view` property.
    *
    * @since 4.30
    */