@arcgis/map-components 5.2.0-next.9 → 5.2.0-next.91

package/dist/components/arcgis-direct-line-measurement-3d/customElement.d.ts

@@ -132,6 +132,15 @@ export abstract class ArcgisDirectLineMeasurement3d extends LitElement {
    * prevent memory leaks.
    *
    * @default false
+   * @example
+   * ```html
+   * <arcgis-direct-line-measurement-3d auto-destroy-disabled></arcgis-direct-line-measurement-3d>
+   * ```
+   *
+   * ```js
+   * directLineMeasurement-3dElement.autoDestroyDisabled = true;
+   * ```
+   * 
    */
   accessor autoDestroyDisabled: boolean;
   /**
@@ -218,8 +227,8 @@ export abstract class ArcgisDirectLineMeasurement3d extends LitElement {
    */
   accessor unitOptions: Array<SystemOrLengthUnit>;
   /**
-   * 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-direct-line-measurement-3d 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-direct-line-measurement-3d component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /** Clears the current measurement. */

package/dist/components/arcgis-directional-pad/customElement.d.ts

@@ -28,6 +28,15 @@ export abstract class ArcgisDirectionalPad extends LitElement {
    * prevent memory leaks.
    *
    * @default false
+   * @example
+   * ```html
+   * <arcgis-directional-pad auto-destroy-disabled></arcgis-directional-pad>
+   * ```
+   *
+   * ```js
+   * directionalPadElement.autoDestroyDisabled = true;
+   * ```
+   * 
    */
   accessor autoDestroyDisabled: boolean;
   /**
@@ -121,8 +130,8 @@ export abstract class ArcgisDirectionalPad extends LitElement {
   /** The current state of the component. */
   get state(): DirectionalPadViewModelState;
   /**
-   * 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-directional-pad 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-directional-pad 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-directions/customElement.d.ts

@@ -32,6 +32,7 @@ import type { SystemOrLengthUnit } from "@arcgis/core/core/units.js";
  *
  * **Note:** Printing in Directions is in beta and considered experimental. The print preview dialog, in some scenarios, may not display as aniticipated.
  *
+ * @see [Sample - Directions component with RouteLayer](https://developers.arcgis.com/javascript/latest/sample-code/directions-routelayer/)
  * @since 4.28
  */
 export abstract class ArcgisDirections extends LitElement {
@@ -64,6 +65,15 @@ export abstract class ArcgisDirections extends LitElement {
    * prevent memory leaks.
    *
    * @default false
+   * @example
+   * ```html
+   * <arcgis-directions auto-destroy-disabled></arcgis-directions>
+   * ```
+   *
+   * ```js
+   * directionsElement.autoDestroyDisabled = true;
+   * ```
+   * 
    */
   accessor autoDestroyDisabled: boolean;
   /**
@@ -97,7 +107,7 @@ export abstract class ArcgisDirections extends LitElement {
    *
    * @default 2
    * @since 4.20
-   * @see [Heading Elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)
+   * @see [Heading Elements](https://developer.mozilla.org/docs/Web/HTML/Element/Heading_Elements)
    * @example
    * // address text will render as an <h3>
    * directions.headingLevel = 3;
@@ -233,8 +243,8 @@ export abstract class ArcgisDirections extends LitElement {
    */
   accessor useDefaultRouteLayer: 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-directions 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-directions 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-distance-measurement-2d/customElement.d.ts

@@ -95,6 +95,15 @@ export abstract class ArcgisDistanceMeasurement2d extends LitElement {
    * prevent memory leaks.
    *
    * @default false
+   * @example
+   * ```html
+   * <arcgis-distance-measurement-2d auto-destroy-disabled></arcgis-distance-measurement-2d>
+   * ```
+   *
+   * ```js
+   * distanceMeasurement-2dElement.autoDestroyDisabled = true;
+   * ```
+   * 
    */
   accessor autoDestroyDisabled: boolean;
   /**
@@ -189,8 +198,8 @@ export abstract class ArcgisDistanceMeasurement2d extends LitElement {
    */
   accessor unitOptions: Array<SystemOrLengthUnit>;
   /**
-   * 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-distance-measurement-2d 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-distance-measurement-2d component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
   /** Clears the current measurement. */

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

@@ -33,8 +33,23 @@ export abstract class ArcgisEditor extends LitElement {
    * prevent memory leaks.
    *
    * @default false
+   * @example
+   * ```html
+   * <arcgis-editor auto-destroy-disabled></arcgis-editor>
+   * ```
+   *
+   * ```js
+   * editorElement.autoDestroyDisabled = true;
+   * ```
+   * 
    */
   accessor autoDestroyDisabled: boolean;
+  /**
+   * A reference to the selection manager currently in use by Editor.
+   *
+   * @internal
+   */
+  get effectiveSelectionManager(): SelectionManager;
   /**
    * Indicates the heading level to use for title of the component. By default, the title (i.e. "Editor") is rendered
    * as a level 4 heading (e.g. `<h4>Editor</h4>`). Depending on the component's placement
@@ -43,7 +58,7 @@ export abstract class ArcgisEditor extends LitElement {
    *
    * @default 4
    * @since 4.20
-   * @see [Heading Elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)
+   * @see [Heading Elements](https://developer.mozilla.org/docs/Web/HTML/Element/Heading_Elements)
    * @example
    * // "Editor" will render as an <h3>
    * editor.headingLevel = 3;
@@ -77,6 +92,20 @@ export abstract class ArcgisEditor extends LitElement {
    * @since 5.0
    */
   accessor hideMergeButton: boolean;
+  /**
+   * Controls whether to use the fully featured selection experience. This includes the
+   * selection toolbar — which provides multiple selection tools — and the
+   * selection list, which allows modifying selections and starting
+   * multi-feature editing workflows, like bulk updates and merges.
+   *
+   * If set to `true`, the component will use a simplified selection experience,
+   * consisting of a single "Select" button.
+   *
+   * @default false
+   * @internal
+   * @since 5.1
+   */
+  accessor hideSelectionToolbar: boolean;
   /**
    * Indicates whether to hide the settings menu. This menu contains the snapping and tooltips settings.
    *
@@ -113,6 +142,69 @@ export abstract class ArcgisEditor extends LitElement {
    * @since 5.0
    */
   accessor hideSnappingControlsElementsFeatureEnabledToggle: boolean;
+  /**
+   * Indicates whether to hide the `gridControls` (configuration of the snapping grid).
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControls: boolean;
+  /**
+   * Indicates whether to hide the `colorSelection` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsColorSelection: boolean;
+  /**
+   * Indicates whether to hide the `dynamicScaleToggle` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsDynamicScaleToggle: boolean;
+  /**
+   * Indicates whether to hide the `lineIntervalInput` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsLineIntervalInput: boolean;
+  /**
+   * Indicates whether to hide the `numericInputs` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsNumericInputs: boolean;
+  /**
+   * Indicates whether to hide the `outOfScaleWarning` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsOutOfScaleWarning: boolean;
+  /**
+   * Indicates whether to hide the `placementButtons` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsPlacementButtons: boolean;
+  /**
+   * Indicates whether to hide the `rotateWithMapToggle` within the snapping grid controls.
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridControlsElementsRotateWithMapToggle: boolean;
+  /**
+   * Indicates whether to hide the `gridEnabledToggle` (snap-to-grid).
+   *
+   * @default false
+   * @since 5.1
+   */
+  accessor hideSnappingControlsElementsGridEnabledToggle: boolean;
   /**
    * Indicates whether to hide the [FeatureSnappingLayerSource](https://developers.arcgis.com/javascript/latest/references/core/views/interactive/snapping/FeatureSnappingLayerSource/) layerList. The layerlist provides the available layer sources supported for snapping.
    *
@@ -315,8 +407,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;
   /**