@arcgis/map-components 5.2.0-next.60 → 5.2.0-next.62

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

@@ -554,8 +554,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-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
    */

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

@@ -1,26 +1,25 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
-import { c as p } from "../../chunks/runtime.js";
-import { css as g, html as _ } from "lit";
-import { LitElement as y } from "@arcgis/lumina";
-import { t as m } from "../../chunks/async-utils.js";
-import { property as c, subclass as f } from "@arcgis/core/core/accessorSupport/decorators.js";
-import * as u from "@arcgis/toolkit/log";
+import { c as g } from "../../chunks/runtime.js";
+import { css as p, html as _ } from "lit";
+import { LitElement as f } from "@arcgis/lumina";
+import { t as d } from "../../chunks/async-utils.js";
+import { property as c, subclass as u } from "@arcgis/core/core/accessorSupport/decorators.js";
+import * as y from "@arcgis/toolkit/log";
 import w from "@arcgis/core/core/Accessor.js";
 import "@arcgis/core/views/MapView.js";
-import v from "@arcgis/core/geometry/SpatialReference.js";
-import { watch as d } from "@arcgis/core/core/reactiveUtils.js";
-import { rotateDimensions as L, registerPanConstraint as C } from "@arcgis/core/applications/Components/OrientedImageryViewer/ImageViewer/utils.js";
-import R from "@arcgis/core/layers/support/TileInfo.js";
-import { u as M } from "../../chunks/useT9n.js";
+import C from "@arcgis/core/geometry/SpatialReference.js";
+import { watch as m } from "@arcgis/core/core/reactiveUtils.js";
+import { rotateDimensions as R, registerPanConstraint as v } from "@arcgis/core/applications/Components/OrientedImageryViewer/ImageViewer/utils.js";
+import M from "@arcgis/core/layers/support/TileInfo.js";
+import { u as P } from "../../chunks/useT9n.js";
 import "@arcgis/core/Graphic.js";
-import G from "@arcgis/core/layers/GraphicsLayer.js";
-import { GenericController as b } from "@arcgis/lumina/controllers";
-import { createRef as P, ref as I } from "lit/directives/ref.js";
-const x = g`:host{height:100%;--arcgis-view-color-focus: none}`;
-var O = Object.defineProperty, z = Object.getOwnPropertyDescriptor, h = (r, e, i, t) => {
-  for (var a = t > 1 ? void 0 : t ? z(e, i) : e, s = r.length - 1, o; s >= 0; s--)
-    (o = r[s]) && (a = (t ? o(e, i, a) : o(a)) || a);
-  return t && a && O(e, i, a), a;
+import { G as b } from "../../chunks/graphicsLayerController.js";
+import { createRef as I, ref as L } from "lit/directives/ref.js";
+const G = p`:host{height:100%;--arcgis-view-color-focus: none}`;
+var x = Object.defineProperty, z = Object.getOwnPropertyDescriptor, h = (t, e, i, r) => {
+  for (var a = r > 1 ? void 0 : r ? z(e, i) : e, s = t.length - 1, o; s >= 0; s--)
+    (o = t[s]) && (a = (r ? o(e, i, a) : o(a)) || a);
+  return r && a && x(e, i, a), a;
 };
 let n = class extends w {
   //--------------------------------------------------------------------------
@@ -28,11 +27,11 @@ let n = class extends w {
   //  Lifecycle
   //
   //--------------------------------------------------------------------------
-  constructor(r) {
-    super(r), this.autoLoad = !1;
+  constructor(t) {
+    super(t), this.autoLoad = !1;
   }
-  static isNonPanoramicMedia(r) {
-    return !!r && typeof r == "object" && "declaredClass" in r && typeof r.declaredClass == "string" && r.declaredClass === "components.oriented-imagery-viewer.support.NonPanoramicMedia";
+  static isNonPanoramicMedia(t) {
+    return !!t && typeof t == "object" && "declaredClass" in t && typeof t.declaredClass == "string" && t.declaredClass === "components.oriented-imagery-viewer.support.NonPanoramicMedia";
   }
   destroy() {
     this._cache?.destroy(), this._cache = void 0;
@@ -43,46 +42,46 @@ let n = class extends w {
   get size() {
     if (!this._cache || this._cache.destroyed || this._cache.loadError || !this._cache.serviceRasterInfo)
       return;
-    const { serviceRasterInfo: r } = this._cache;
-    return [r.width, r.height];
+    const { serviceRasterInfo: t } = this._cache;
+    return [t.width, t.height];
   }
   //---------------------------------------------------------------------------
   //
   //  Public Methods
   //
   //---------------------------------------------------------------------------
-  async load(r) {
+  async load(t) {
     if (this._cache && !this._cache.destroyed)
-      return await this._cache.load(r), { layer: this._cache, size: this.size };
+      return await this._cache.load(t), { layer: this._cache, size: this.size };
     const { url: e, customParameters: i } = this;
-    let t = this.datasetFormat;
+    let r = this.datasetFormat;
     if (!e)
       throw new Error("URL is required to load NonPanoramicMedia.");
-    if (!t) {
+    if (!r) {
       const o = await import("../../chunks/urlUtils.js");
-      if (m(r), t = o.guessExtensionFromURI(e), !t) {
+      if (d(t), r = o.guessExtensionFromURI(e), !r) {
         try {
-          t = await o.getDatasetFormat(e);
+          r = await o.getDatasetFormat(e);
         } catch {
-          u.log("warn", this, "Failed to determine dataset format from URL or response headers."), t = "UNKNOWN FORMAT";
+          y.log("warn", this, "Failed to determine dataset format from URL or response headers."), r = "UNKNOWN FORMAT";
         }
-        m(r);
+        d(t);
       }
     }
-    this.datasetFormat = t;
+    this.datasetFormat = r;
     const a = (await import("@arcgis/core/layers/ImageryTileLayer.js")).default;
-    m(r);
+    d(t);
     const s = new a({
       url: e,
       // @ts-ignore - datasetFormat is not part of the official ImageryTileLayer properties, but is used in the custom ioConfig for loading the image and is necessary to pass along the format information.
       ioConfig: {
         skipExtensions: ["aux.xml", "jgw"],
         skipMapInfo: !0,
-        datasetFormat: t
+        datasetFormat: r
       },
       customParameters: i ?? void 0
     });
-    return await s.load(r), m(r), this._cache = s, { layer: this._cache, size: this.size };
+    return await s.load(t), d(t), this._cache = s, { layer: this._cache, size: this.size };
   }
 };
 h([
@@ -107,103 +106,36 @@ h([
   c()
 ], n.prototype, "size", 1);
 n = h([
-  f("components.oriented-imagery-viewer.support.NonPanoramicMedia")
+  u("components.oriented-imagery-viewer.support.NonPanoramicMedia")
 ], n);
-function A(r, e, i, t, a) {
-  const { width: s, height: o } = L(r, e, a);
-  return Math.max(s / i, o / t);
+function O(t, e, i, r, a) {
+  const { width: s, height: o } = R(t, e, a);
+  return Math.max(s / i, o / r);
 }
-const F = 96, E = 39.37, l = E * F;
-function N(r) {
-  const e = l * 0.25, i = l * r, t = [];
+const F = 96, A = 39.37, l = A * F;
+function E(t) {
+  const e = l * 0.25, i = l * t, r = [];
   let a = i;
   for (; a > e; )
-    t.push(a), a *= 0.5;
-  t.push(e);
-  const { lods: s } = R.create({
-    scales: t
+    r.push(a), a *= 0.5;
+  r.push(e);
+  const { lods: s } = M.create({
+    scales: r
   });
   return {
     minScale: i,
     lods: s
   };
 }
-class H extends b {
-  get graphics() {
-    return this._graphicsLayer?.graphics;
-  }
-  _ensureGraphicsLayer() {
-    (!this._graphicsLayer || this._graphicsLayer.destroyed) && (this._graphicsLayer = new G({
-      title: "Overlays",
-      listMode: "hide",
-      visible: !0,
-      blendMode: "source-atop"
-    }));
-  }
-  hostLoaded() {
-    this._ensureGraphicsLayer(), this.component.manager.onLifecycle(() => [
-      d(
-        () => this.component?.map,
-        (e, i) => {
-          i?.layers.remove(this._graphicsLayer), e && e?.layers.add(this._graphicsLayer);
-        },
-        { initial: !0, sync: !0 }
-      ),
-      d(
-        () => this.component?.map?.allLayers.length,
-        (e) => {
-          e && this.component?.map?.layers.reorder(this._graphicsLayer, e - 1);
-        },
-        { initial: !0, sync: !0 }
-      )
-    ]);
-  }
-  /**
-   * Adds a graphic to the graphics layer.
-   */
-  addGraphic(e) {
-    this._graphicsLayer.add(e);
-  }
-  /**
-   * Adds graphics to the graphics layer.
-   */
-  addGraphics(e) {
-    this._graphicsLayer.addMany(e);
-  }
-  /**
-   * Removes a graphic from the graphics layer.
-   */
-  removeGraphic(e) {
-    this._graphicsLayer?.destroyed || this._graphicsLayer.remove(e);
-  }
-  /**
-   * Removes graphics from the graphics layer.
-   */
-  removeGraphics(e) {
-    this._graphicsLayer?.destroyed || this._graphicsLayer.removeMany(e);
-  }
-  /**
-   * Removes all graphics from the graphics layer.
-   */
-  clearGraphics() {
-    this._graphicsLayer?.destroyed || this._graphicsLayer.removeAll();
-  }
-  /**
-   * Destroys the graphics layer.
-   */
-  destroy() {
-    this._graphicsLayer?.destroy();
-  }
-}
-class S extends y {
+class N extends f {
   constructor() {
-    super(...arguments), this._messages = M(), this._graphicsController = new H(this), this._imageChanged = !1, this._internalMap = P(), this._loading = !1, this.hideHeader = !1, this.hideLoader = !1, this.hideZoomControls = !1, this.rotation = 0;
+    super(...arguments), this._messages = P(), this._graphicsController = new b(this), this._imageChanged = !1, this._internalMap = I(), this._loading = !1, this.hideHeader = !1, this.hideLoader = !1, this.hideZoomControls = !1, this.rotation = 0;
   }
   static {
     this.properties = { _imageChanged: 16, _internalMap: 16, _image: 16, _loading: 16, _media: 16, hideHeader: 5, hideLoader: 5, hideZoomControls: 5, messageOverrides: 0, media: 0, rotation: 9 };
   }
   static {
-    this.styles = [x];
+    this.styles = [G];
   }
   get imageRenderer() {
     return this._internalMap?.value?.view;
@@ -244,7 +176,7 @@ class S extends y {
       this._createResizeConstraint(),
       this._createRotationHandler(),
       this._createPanConstraint(),
-      d(() => this._media, (e) => {
+      m(() => this._media, (e) => {
         this._mediaAbortController?.abort(), e && (this._mediaAbortController = new AbortController(), this._mediaPromise = this._loadMediaInternal(e, this._mediaAbortController));
       }, {
         initial: !0,
@@ -253,28 +185,28 @@ class S extends y {
     ]);
   }
   _createPanConstraint() {
-    return d(() => ({ image: this._image, imageRenderer: this.imageRenderer }), ({ image: e, imageRenderer: i }) => {
-      !e || !i?.ready || C(i, e);
+    return m(() => ({ image: this._image, imageRenderer: this.imageRenderer }), ({ image: e, imageRenderer: i }) => {
+      !e || !i?.ready || v(i, e);
     }, { sync: !0, initial: !0 });
   }
   _createResizeConstraint() {
-    return d(() => {
+    return m(() => {
       if (!this.imageRenderer?.ready || !this._image)
         return;
-      const { width: e, height: i } = this._image.serviceRasterInfo, { width: t, height: a, rotation: s } = this.imageRenderer;
-      return A(e, i, t, a, s);
+      const { width: e, height: i } = this._image.serviceRasterInfo, { width: r, height: a, rotation: s } = this.imageRenderer;
+      return O(e, i, r, a, s);
     }, (e) => {
       if (!e || !this.imageRenderer)
         return;
-      const { constraints: i, scale: t } = this.imageRenderer, a = i.minScale, { lods: s, minScale: o } = N(e);
+      const { constraints: i, scale: r } = this.imageRenderer, a = i.minScale, { lods: s, minScale: o } = E(e);
       i.set({
         minScale: o,
         lods: s
-      }), this.imageRenderer.scale = this._imageChanged || Math.abs(t - a) <= 1e-6 ? o : t, this._imageChanged = !1;
+      }), this.imageRenderer.scale = this._imageChanged || Math.abs(r - a) <= 1e-6 ? o : r, this._imageChanged = !1;
     }, { sync: !0, initial: !0 });
   }
   _createRotationHandler() {
-    return d(() => this.rotation, (e) => {
+    return m(() => this.rotation, (e) => {
       this.imageRenderer && (this.imageRenderer.constraints.rotationEnabled = !0, this.imageRenderer.rotation = e, this.imageRenderer.constraints.rotationEnabled = !1);
     }, { sync: !0, initial: !0 });
   }
@@ -284,16 +216,16 @@ class S extends y {
   async _loadMediaInternal(e, i) {
     if (this._loading = !0, this._clearImage(), !e)
       throw new Error("No media provided");
-    const { layer: t } = await e.load(i).finally(() => {
+    const { layer: r } = await e.load(i).finally(() => {
       this._loading = !1;
     });
-    m(i), this._imageChanged = !0, this._image = t, this.imageRenderer?.map?.layers.add(this._image);
+    d(i), this._imageChanged = !0, this._image = r, this.imageRenderer?.map?.layers.add(this._image);
   }
   render() {
-    return _`<calcite-panel .loading=${this.hideLoader ? void 0 : this._loading} .heading=${this.hideHeader ? void 0 : this._messages.title}><arcgis-map hide-attribution .spatialReference=${v.WebMercator} ${I(this._internalMap)}><arcgis-zoom .hidden=${this.hideZoomControls} .messageOverrides=${this.messageOverrides} slot=top-left></arcgis-zoom></arcgis-map></calcite-panel>`;
+    return _`<calcite-panel .loading=${this.hideLoader ? void 0 : this._loading} .heading=${this.hideHeader ? void 0 : this._messages.title}><arcgis-map hide-attribution .spatialReference=${C.WebMercator} ${L(this._internalMap)}><arcgis-zoom .hidden=${this.hideZoomControls} .messageOverrides=${this.messageOverrides} slot=top-left></arcgis-zoom></arcgis-map></calcite-panel>`;
   }
 }
-p("arcgis-oriented-imagery-viewer-image-viewer", S);
+g("arcgis-oriented-imagery-viewer-image-viewer", N);
 export {
-  S as ArcgisOrientedImageryViewerImageViewer
+  N as ArcgisOrientedImageryViewerImageViewer
 };