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

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

@@ -0,0 +1 @@
+export * from "./customElement.js";

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer/index.js

@@ -0,0 +1,5 @@
+import "@esri/calcite-components/components/calcite-panel";
+import "../arcgis-scene/index.js";
+import "../arcgis-oriented-imagery-viewer-panoramic-viewer-zoom/index.js";
+import "../arcgis-oriented-imagery-viewer-video-controls/index.js";
+export * from "./customElement.js";

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer/support/PanoramicMedia.d.ts

@@ -0,0 +1,49 @@
+import type Accessor from "@arcgis/core/core/Accessor.js";
+import type Mesh from "@arcgis/core/geometry/Mesh.js";
+import type PanoramicTileSource from "./PanoramicTileSource.js";
+import type { AbortOptions } from "../../../utils/async-utils.js";
+
+export interface PanoramicMediaProperties extends Partial<Pick<PanoramicMedia, "autoLoad" | "cameraHeading" | "extension" | "id" | "matrix" | "type" | "uiStrings" | "url">> {}
+
+export default class PanoramicMedia extends Accessor {
+  /** @param value */
+  static isPanoramicMedia(value: unknown): value is PanoramicMedia;
+  constructor(properties: PanoramicMediaProperties);
+  /** @default false */
+  accessor autoLoad: boolean;
+  accessor cameraHeading: number | undefined;
+  get element(): HTMLImageElement | HTMLVideoElement | undefined;
+  accessor extension: string | undefined;
+  get horizonPitch(): number;
+  get horizonRoll(): number;
+  get horizonYaw(): number;
+  accessor id: number | undefined;
+  accessor matrix: [number, number, number, number, number, number, number, number, number] | undefined;
+  get panoramicTileSource(): PanoramicTileSource | undefined;
+  get size(): [number, number];
+  /** @default "image" */
+  accessor type: "image" | "video";
+  accessor uiStrings: Record<string, string>;
+  accessor url: string;
+  destroy(): void;
+  /** @param options */
+  load(options?: AbortOptions): Promise<{
+      mesh: Mesh;
+      size: [number, number];
+  }>;
+  /** @param options */
+  protected loadImageMesh(options?: AbortOptions): Promise<{
+      mesh: Mesh;
+      size: [number, number];
+  }>;
+  /** @param options */
+  protected loadOptimizedImageMesh(options?: AbortOptions): Promise<{
+      mesh: Mesh;
+      size: [number, number];
+  }>;
+  /** @param options */
+  protected loadVideoMesh(options?: AbortOptions): Promise<{
+      mesh: Mesh;
+      size: [number, number];
+  }>;
+}

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer/support/PanoramicTilePlanner.d.ts

@@ -0,0 +1,18 @@
+export type TileKey = `${number}/${number}/${number}`;
+
+export type RequestUpdateProperties = {
+  heading: number;
+  pitch: number;
+  hfov: number;
+  vfov: number;
+  imageSize: [number, number];
+  viewportSize: [number, number];
+};
+
+export type TileUpdatePlan = {
+  stableLevel: number;
+  desiredKeySet: Set<TileKey>;
+  toFetch: TileKey[];
+  toKeep: TileKey[];
+  toDrop: TileKey[];
+};

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer/support/PanoramicTileSource.d.ts

@@ -0,0 +1,36 @@
+import type Mesh from "@arcgis/core/geometry/Mesh.js";
+import type ImageryTileLayer from "@arcgis/core/layers/ImageryTileLayer.js";
+import type { RequestUpdateProperties, TileKey, TileUpdatePlan } from "./PanoramicTilePlanner.js";
+
+export default class PanoramicTileSource {
+  constructor(_layer: ImageryTileLayer);
+  get baseMesh(): Mesh;
+  get currentLevel(): number | undefined;
+  fetchTileImageData: (level: number, row: number, col: number, signal?: AbortSignal) => Promise<ImageData>;
+  get imageSize(): [number, number];
+  loadComponent: (level: number, row: number, col: number, imageData: ImageData) => void;
+  unloadComponent: (level: number, row: number, col: number) => void;
+  /** @param desiredKeySet */
+  cancelStaleInflight(desiredKeySet: Set<TileKey>): void;
+  destroy(): void;
+  /**
+   * @param level
+   * @param row
+   * @param col
+   */
+  getTileAnchor(level: number, row: number, col: number): [number, number, number];
+  load(): Promise<this>;
+  /** @param key */
+  markTileDropped(key: TileKey): void;
+  /**
+   * @param key
+   * @param controller
+   */
+  markTileInflight(key: TileKey, controller: AbortController): void;
+  /** @param key */
+  markTileInflightResolved(key: TileKey): void;
+  /** @param key */
+  markTileLoaded(key: TileKey): void;
+  /** @param input */
+  planTiles(input: RequestUpdateProperties): TileUpdatePlan;
+}

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

@@ -0,0 +1,91 @@
+/// <reference path="../../index.d.ts" />
+import type SceneView from "@arcgis/core/views/SceneView.js";
+import type { PublicLitElement as LitElement } from "@arcgis/lumina";
+import type { Layout, State } from "../arcgis-zoom/types.js";
+import type { ArcgisReferenceElement } from "../types.js";
+import type { T9nMeta } from "@arcgis/lumina/controllers";
+import type { Button as Button } from "@esri/calcite-components/components/calcite-button";
+
+/** @internal */
+export abstract class ArcgisOrientedImageryViewerPanoramicViewerZoom extends LitElement {
+  /**
+   * If true, the component will not be destroyed automatically when it is
+   * disconnected from the document. This is useful when you want to move the
+   * component to a different place on the page, or temporarily hide it. If this
+   * is set, make sure to call the [destroy()](https://developers.arcgis.com/javascript/latest/references/map-components/components/arcgis-oriented-imagery-viewer-panoramic-viewer-zoom/#destroy) method when you are done to
+   * prevent memory leaks.
+   *
+   * @default false
+   */
+  accessor autoDestroyDisabled: boolean;
+  get hfov(): number | undefined;
+  /**
+   * Icon which represents the component.
+   * Typically used when the component is controlled by another component (e.g. by the Expand component).
+   *
+   * @default "magnifying-glass-plus"
+   * @see [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)
+   */
+  accessor icon: string | undefined;
+  /** The component's default label. */
+  accessor label: string | undefined;
+  /**
+   * Determines the layout/orientation of the Zoom component.
+   *
+   * @default "vertical"
+   */
+  accessor layout: Layout;
+  /**
+   * Replace localized message strings with your own strings.
+   *
+   * _**Note**: Individual message keys may change between releases._
+   */
+  accessor messageOverrides: {
+      componentLabel?: string | undefined;
+      zoomIn?: string | undefined;
+      zoomOut?: string | undefined;
+  };
+  /** @internal */
+  protected messages: Partial<{
+      componentLabel: string;
+      zoomIn: string;
+      zoomOut: string;
+  }> & T9nMeta<{
+      componentLabel: string;
+      zoomIn: string;
+      zoomOut: string;
+  }>;
+  /**
+   * By assigning the `id` attribute of the Map or Scene component to this property, you can position a child component anywhere in the DOM while still maintaining a connection to the Map or Scene.
+   *
+   * @see [Associate components with a Map or Scene component](https://developers.arcgis.com/javascript/latest/programming-patterns/#associate-components-with-a-map-or-scene-component)
+   */
+  accessor referenceElement: ArcgisReferenceElement | string | undefined;
+  /** The current state of the component. */
+  get state(): State;
+  get vfov(): number | 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-oriented-imagery-viewer-panoramic-viewer-zoom component will be associated with a map or scene component rather than using the `view` property.
+   */
+  accessor view: SceneView | undefined;
+  /**
+   * Specifies the size of the component.
+   *
+   * @default "m"
+   * @since 5.0
+   */
+  accessor visualScale: Button["scale"];
+  get zoomLevel(): number | undefined;
+  /** Permanently destroy the component. */
+  destroy(): Promise<void>;
+  /** @param fov */
+  zoomFOV(fov: number): void;
+  zoomIn(): void;
+  zoomOut(): void;
+  /** Emitted when the component associated with a map or scene view is ready to be interacted with. */
+  readonly arcgisReady: import("@arcgis/lumina").TargetedEvent<this, void>;
+  readonly "@eventTypes": {
+    arcgisReady: ArcgisOrientedImageryViewerPanoramicViewerZoom["arcgisReady"]["detail"];
+  };
+}

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer-zoom/customElement.js

@@ -0,0 +1,93 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+import { c } from "../../chunks/runtime.js";
+import { html as h } from "lit";
+import { LitElement as l, createEvent as v, nothing as r, safeClassMap as u } from "@arcgis/lumina";
+import { g as f } from "../../chunks/globalCss.js";
+import { s as w, c as d, a as g } from "../../chunks/zoom.js";
+import { u as O } from "../../chunks/useT9n.js";
+import { u as V } from "../../chunks/useView.js";
+import { m as s, f as i, a as n, b as p, c as y, d as m } from "../../chunks/utils3.js";
+import { clamp as z } from "@arcgis/toolkit/number";
+class F extends l {
+  constructor() {
+    super(...arguments), this.messages = O({
+      name: "zoom"
+    }), this._state = "disabled", this.view = V(this), this.autoDestroyDisabled = !1, this.icon = "magnifying-glass-plus", this.layout = "vertical", this.visualScale = "m", this.arcgisReady = v();
+  }
+  static {
+    this.properties = { _state: 16, _canZoomIn: 16, _canZoomOut: 16, _maxFOV: 16, _minFOV: 16, zoomLevel: 32, view: 0, autoDestroyDisabled: 5, icon: 1, label: 1, layout: 3, messageOverrides: 0, referenceElement: 1, visualScale: 1, state: 32, hfov: 32, vfov: 32 };
+  }
+  static {
+    this.styles = w;
+  }
+  get _canZoomIn() {
+    return this.view?.ready ? this._minFOV === 0 ? !0 : this.view.camera.fov > this._minFOV : !1;
+  }
+  get _canZoomOut() {
+    return this.view?.ready ? this._maxFOV === 0 ? !0 : this.view.camera.fov < this._maxFOV : !1;
+  }
+  get _maxFOV() {
+    if (!this.view?.ready)
+      return s;
+    const t = this.view.width / this.view.height;
+    return i(s, t);
+  }
+  get _minFOV() {
+    if (!this.view?.ready)
+      return n;
+    const t = this.view.width / this.view.height;
+    return i(n, t);
+  }
+  get zoomLevel() {
+    if (!this.view?.ready)
+      return;
+    const { hfov: t } = this;
+    return Math.max(1, Math.log(s / t) / Math.log(2));
+  }
+  get state() {
+    return this._state;
+  }
+  get hfov() {
+    const { view: t } = this;
+    if (!t?.ready)
+      return;
+    const e = t.width / t.height;
+    return p(t.camera.fov, e);
+  }
+  get vfov() {
+    const { view: t } = this;
+    if (!t?.ready)
+      return;
+    const e = t.width / t.height;
+    return y(t.camera.fov, e);
+  }
+  async destroy() {
+    await this.manager.destroy();
+  }
+  zoomFOV(t) {
+    this.view?.ready && (this.view.camera.fov = z(t, this._minFOV, this._maxFOV), this.view.camera = this.view.camera.clone());
+  }
+  zoomIn() {
+    if (!this._canZoomIn || !this.view)
+      return;
+    const t = this.view.width / this.view.height;
+    this.zoomFOV(this.view.camera.fov - i(m, t));
+  }
+  zoomOut() {
+    if (!this._canZoomOut || !this.view)
+      return;
+    const t = this.view.width / this.view.height;
+    this.zoomFOV(this.view.camera.fov + i(m, t));
+  }
+  render() {
+    const t = d(this.view), e = g(this.view), { zoomIn: a, zoomOut: o } = this.messages;
+    return h`<div class=${u({
+      [f.arcgisButton]: !0,
+      horizontal: this.layout === "horizontal"
+    })}><calcite-button class="zoom-in" .disabled=${!t} icon-start=plus kind=neutral .label=${a} @click=${this.zoomIn} .scale=${this.visualScale} title=${a ?? r}></calcite-button><calcite-button class="zoom-out" .disabled=${!e} icon-start=minus kind=neutral .label=${o} @click=${this.zoomOut} .scale=${this.visualScale} title=${o ?? r}></calcite-button></div>`;
+  }
+}
+c("arcgis-oriented-imagery-viewer-panoramic-viewer-zoom", F);
+export {
+  F as ArcgisOrientedImageryViewerPanoramicViewerZoom
+};

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer-zoom/index.d.ts

@@ -0,0 +1 @@
+export * from "./customElement.js";

package/dist/components/arcgis-oriented-imagery-viewer-panoramic-viewer-zoom/index.js

@@ -0,0 +1,2 @@
+import "@esri/calcite-components/components/calcite-button";
+export * from "./customElement.js";

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

@@ -273,8 +273,8 @@ export abstract class ArcgisPaste extends LitElement {
   /** The list of supported paste operations. New types of operations can be registered using the 'registerPasteOperation' */
   accessor supportedCommands: SupportedPasteCommand | SupportedPasteCommand[];
   /**
-   * 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-paste 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-paste component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /** Cancels any running Clipboard Move Interaction */

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

@@ -142,7 +142,7 @@ export abstract class ArcgisPopup 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).
+   * 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).
    *
    * @default false
    */
@@ -567,8 +567,8 @@ export abstract class ArcgisPopup extends LitElement {
    */
   accessor updateLocationEnabled: 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-popup 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-popup 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-popup/customElement.js

@@ -1,7 +1,7 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
 import { c as A } from "../../chunks/runtime.js";
 import { css as E, html as w } from "lit";
-import P from "@arcgis/core/popup/Features.js";
+import P from "@arcgis/core/popup/FeatureContentCollection.js";
 import { u as O } from "../../chunks/useT9n.js";
 import { useDirection as F, usePropertyChange as $ } from "@arcgis/lumina/controllers";
 import { m as N } from "../../chunks/useViewModel.js";

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

@@ -95,8 +95,8 @@ export abstract class ArcgisPresentation extends LitElement {
    */
   accessor slidePopupDisabled: 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-presentation 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-presentation component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /** Permanently destroy the component */

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

@@ -593,8 +593,8 @@ export abstract class ArcgisPrint extends LitElement {
   get templateOptions(): TemplateOptions;
   set templateOptions(value: Partial<TemplateOptions>);
   /**
-   * 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-print 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-print component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | null | undefined;
   /**

package/dist/components/arcgis-print-dpi-input/customElement.js

@@ -3,7 +3,7 @@ import { c as p } from "../../chunks/runtime.js";
 import { html as m } from "lit";
 import { watch as o } from "@arcgis/core/core/reactiveUtils.js";
 import { LitElement as h } from "@arcgis/lumina";
-import { i as u } from "../../chunks/utils3.js";
+import { i as u } from "../../chunks/utils4.js";
 class d extends h {
   constructor() {
     super(...arguments), this._dpi = 1;

package/dist/components/arcgis-print-export-button/customElement.js

@@ -2,7 +2,7 @@
 import { c } from "../../chunks/runtime.js";
 import { css as p, html as o } from "lit";
 import { LitElement as d } from "@arcgis/lumina";
-import { r as m } from "../../chunks/utils3.js";
+import { r as m } from "../../chunks/utils4.js";
 const h = p`.export-button-container{display:flex;flex-direction:column;align-items:center;gap:.5rem}`;
 class u extends d {
   static {

package/dist/components/arcgis-print-format-select/customElement.js

@@ -3,7 +3,7 @@ import { c as m } from "../../chunks/runtime.js";
 import { html as i } from "lit";
 import { watch as r } from "@arcgis/core/core/reactiveUtils.js";
 import { LitElement as f } from "@arcgis/lumina";
-import { f as n } from "../../chunks/utils3.js";
+import { f as n } from "../../chunks/utils4.js";
 class c extends f {
   constructor() {
     super(...arguments), this._formats = [];

package/dist/components/arcgis-print-main-panel/customElement.js

@@ -2,7 +2,7 @@
 import { c as o } from "../../chunks/runtime.js";
 import { css as c, html as i } from "lit";
 import { LitElement as n } from "@arcgis/lumina";
-import { i as r } from "../../chunks/utils3.js";
+import { i as r } from "../../chunks/utils4.js";
 import { watch as d } from "@arcgis/core/core/reactiveUtils.js";
 const p = c`:host{display:flex;flex-direction:column;flex-grow:1}calcite-tabs{flex-grow:1}calcite-tab{--calcite-tab-content-block-padding: 0}calcite-loader{margin-right:var(--calcite-spacing-xxs)}`;
 class h extends n {

package/dist/components/arcgis-print-template-select/customElement.js

@@ -3,7 +3,7 @@ import { c } from "../../chunks/runtime.js";
 import { css as o, html as a } from "lit";
 import { watch as s } from "@arcgis/core/core/reactiveUtils.js";
 import { LitElement as r } from "@arcgis/lumina";
-import { g as n, a as m, b as p } from "../../chunks/utils3.js";
+import { g as n, a as m, b as p } from "../../chunks/utils4.js";
 import { useDirection as d } from "@arcgis/lumina/controllers";
 const h = o`.template-select-container{border:1px solid var(--calcite-color-border-1);cursor:pointer}.template-select-container .template-select-error,.template-select-container .template-select-arrow{display:flex;align-self:center;margin-right:var(--calcite-spacing-md)}`;
 class g extends r {

package/dist/components/arcgis-print-template-selector/customElement.js

@@ -3,7 +3,7 @@ import { c as m } from "../../chunks/runtime.js";
 import { css as p, html as l } from "lit";
 import { watch as c } from "@arcgis/core/core/reactiveUtils.js";
 import { LitElement as u, nothing as h } from "@arcgis/lumina";
-import { i as o, r as g, a as v, g as f, b as T } from "../../chunks/utils3.js";
+import { i as o, r as g, a as v, g as f, b as T } from "../../chunks/utils4.js";
 const w = p`:host{overflow-y:hidden;display:flex;flex:1 0}.template-select-flow-item-container{display:flex;flex-direction:column;justify-content:space-between;overflow-y:hidden;flex-grow:1}.template-select-flow-item-container .template-select-flow-item-content{display:flex;flex-direction:column;overflow-y:auto;flex:1 0}.template-select-flow-item-container .template-select-flow-item-content .template-select-flow-item-list-heading{display:flex;gap:var(--calcite-spacing-xs);align-items:center;justify-content:space-between;padding:var(--calcite-spacing-md) var(--calcite-spacing-lg);background-color:var(--calcite-color-foreground-2);border-bottom:1px solid var(--calcite-color-border-3);font-weight:var(--calcite-font-weight-semibold)}.template-button-container{padding:var(--calcite-spacing-md)}.template-done-button{width:100%}`;
 class $ extends u {
   static {

package/dist/components/arcgis-scale-bar/customElement.d.ts

@@ -70,8 +70,8 @@ export abstract class ArcgisScaleBar extends LitElement {
    */
   accessor unit: ScaleBarUnit | 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-scale-bar 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-scale-bar 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-scale-range-slider/customElement.d.ts

@@ -129,8 +129,8 @@ export abstract class ArcgisScaleRangeSlider extends LitElement {
    */
   get state(): ScaleRangeSliderViewModelState;
   /**
-   * 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-scale-range-slider 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-scale-range-slider 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-search/customElement.d.ts

@@ -450,8 +450,8 @@ export abstract class ArcgisSearch 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-search 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-search 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-shadow-cast/customElement.d.ts

@@ -516,8 +516,8 @@ export abstract class ArcgisShadowCast extends LitElement {
    */
   accessor utcOffset: number | 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-shadow-cast 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-shadow-cast component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /**

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

@@ -523,8 +523,8 @@ export abstract class ArcgisSketch 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-sketch 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-sketch 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-slice/customElement.d.ts

@@ -279,8 +279,8 @@ export abstract class ArcgisSlice extends LitElement {
    */
   accessor tiltEnabled: 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-slice 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-slice component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /**

package/dist/components/arcgis-slider-scale-range/customElement.d.ts

@@ -247,8 +247,8 @@ export abstract class ArcgisSliderScaleRange extends LitElement {
    */
   get state(): "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-slider-scale-range 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-slider-scale-range component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapView | SceneView | undefined;
   /** Permanently destroy the component. */

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

@@ -136,8 +136,8 @@ export abstract class ArcgisSnappingControls extends LitElement {
    */
   get state(): SnappingControlsViewModelState;
   /**
-   * 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-snapping-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-snapping-controls 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-swipe/customElement.d.ts

@@ -148,8 +148,8 @@ export abstract class ArcgisSwipe extends LitElement {
    */
   accessor trailingLayers: SwipeViewModel["trailingLayers"];
   /**
-   * 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-swipe 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-swipe 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-table-list/customElement.d.ts

@@ -309,8 +309,8 @@ export abstract class ArcgisTableList extends LitElement {
   /** @internal */
   accessor tables: ReadonlyCollection<Layer | Sublayer> | 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-table-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-table-list component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapView | SceneView | undefined;
   /** Permanently destroy the component. */

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

@@ -73,6 +73,20 @@ export abstract class ArcgisTableListNext extends LitElement {
    * @default 2
    */
   accessor headingLevel: HeadingLevel;
+  /**
+   * 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;
   /**
    * Indicates whether the status indicators will be hidden.
    *
@@ -200,8 +214,8 @@ export abstract class ArcgisTableListNext extends LitElement {
   /** A collection of tables to display in the component. */
   accessor tables: ReadonlyCollection<Layer | Sublayer> | 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-table-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-table-list-next component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: LinkChartView | MapView | SceneView | undefined;
   /** Permanently destroy the component. */