@arcgis/map-components 4.34.0-next.160 → 4.34.0-next.161

package/dist/docs/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://raw.githubusercontent.com/JetBrains/web-types/master/schema/web-types.json",
   "name": "@arcgis/map-components",
-  "version": "4.34.0-next.160",
+  "version": "4.34.0-next.161",
   "description-markup": "markdown",
   "contributions": {
     "html": {
@@ -156,7 +156,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Area Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -323,7 +323,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Area Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -766,7 +766,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Basemap Gallery component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -1228,7 +1228,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Basemap Layer List component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -1407,7 +1407,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Basemap Toggle component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -1789,7 +1789,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Bookmarks component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -1994,7 +1994,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Building Explorer component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -2352,7 +2352,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Catalog Layer List component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -2509,7 +2509,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Compass component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -2529,7 +2529,7 @@
         },
         {
           "name": "arcgis-coordinate-conversion",
-          "description": "The CoordinateConversion component provides a way to display user cursor position either as map coordinates or\nas any of several popular coordinate notations.  Additionally, the component provides a way to convert\nuser input coordinates into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n\nSeveral common formats are included by default:\n* XY - Longitude, Latitude (WGS84)\n* MGRS - [Military Grid Reference System](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#mgrs)\n* UTM - [Universal Transverse Mercator](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#utm)\n* DD - Decimal Degrees\n* DDM - Degrees Decimal Minutes\n* DMS - Degrees Minutes Seconds\n* Basemap - X, Y in the coordinate system used by the current basemap in the units used by the basemap.\nWeb Mercator is the standard for Esri-provided basemaps.\n\nAdditional formats can be created by a developer and made available\nthrough the component\n--\n\n### Events\n- **arcgisConversionChange**\n- **arcgisPropertyChange** - Emitted when the value of a property is changed. Use this to listen to changes to properties.\n- **arcgisReady** - Emitted when the component associated with a map or scene view is ready to be interacted with.\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.\n- `destroy(): Promise<void>` - Permanently destroy the component.\n- `reverseConvert(coordinate: string, format: Format): Promise<__esri.Point | nullish>` - Attempt to convert a string into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).  The format of the\nstring must be specified.  A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of available formats can be\nobtained from the [formats](#formats) property.",
+          "description": "The Coordinate Conversion component provides a way to display user cursor position either as map coordinates or\nas any of several popular coordinate notations.  Additionally, the component provides a way to convert\nuser input coordinates into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n\nSeveral common formats are included by default:\n* XY - Longitude, Latitude (WGS84)\n* MGRS - [Military Grid Reference System](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#mgrs)\n* UTM - [Universal Transverse Mercator](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#utm)\n* DD - Decimal Degrees\n* DDM - Degrees Decimal Minutes\n* DMS - Degrees Minutes Seconds\n* Basemap - X, Y in the coordinate system used by the current basemap in the units used by the basemap.\nWeb Mercator is the standard for Esri-provided basemaps.\n\nAdditional formats can be created by a developer and made available\nthrough the component\n--\n\n### Events\n- **arcgisConversionChange** - Emitted when a conversion is added or removed, or when the order of conversions changes.\n- **arcgisPropertyChange** - Emitted when the value of a property is changed. Use this to listen to changes to properties.\n- **arcgisReady** - Emitted when the component associated with a map or scene view is ready to be interacted with.\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.\n- `destroy(): Promise<void>` - Permanently destroy the component.\n- `reverseConvert(coordinate: string, format: Format): Promise<__esri.Point | nullish>` - Attempt to convert a string into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).  The format of the\nstring must be specified.  A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of available formats can be\nobtained from the [formats](#formats) property.",
           "doc-url": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-coordinate-conversion/",
           "attributes": [
             {
@@ -2542,7 +2542,7 @@
             },
             {
               "name": "expanded",
-              "description": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+              "description": "Describes whether the component is expanded or not. If `true`, the component is expanded and all conversions are visible.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2565,7 +2565,7 @@
             },
             {
               "name": "hide-capture-button",
-              "description": "Determines whether the capture button will be shown in the component",
+              "description": "Determines whether the capture button will be shown in the component. If `true`, the capture button will be hidden.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2573,7 +2573,7 @@
             },
             {
               "name": "hide-expand-button",
-              "description": "Determines whether the expand button will be shown in the component",
+              "description": "Determines whether the expand button will be shown in the component. If `true`, the expand button will be hidden.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2581,7 +2581,7 @@
             },
             {
               "name": "hide-input-button",
-              "description": "Determines whether the edit button will be shown in the component",
+              "description": "Determines whether the input coordiante button will be shown in the component. If `true`, the input button will be hidden.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2589,7 +2589,7 @@
             },
             {
               "name": "hide-settings-button",
-              "description": "Determines whether the settings button will be shown in the component",
+              "description": "Determines whether the settings button will be shown in the component. If `true`, the settings button will be hidden.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2622,9 +2622,17 @@
                 ]
               }
             },
+            {
+              "name": "multiple-conversions-disabled",
+              "description": "If this property is set to `true`, multiple conversions will be disabled, and only a single conversion will be displayed. Otherwise, multiple conversions will be shown.",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
             {
               "name": "orientation",
-              "description": "Determines whether the component should expand up or down.  If set to `auto`\nthe component will be oriented based on its position in the view.",
+              "description": "Determines whether the component should expand up or down.  If set to `auto`,\nthe component will be oriented based on its position in the view.",
               "default": "\"auto\"",
               "value": {
                 "type": [
@@ -2658,14 +2666,6 @@
                 "type": "string"
               }
             },
-            {
-              "name": "single-conversion",
-              "description": "If this property is set to `true`, only a single conversion can be displated.  For a simpler experience with only\none conversion at a time, this property can be set to `true`.",
-              "default": "false",
-              "value": {
-                "type": "boolean"
-              }
-            },
             {
               "name": "state",
               "description": "The current state of the component.",
@@ -2701,7 +2701,8 @@
           "events": [
             {
               "name": "arcgisConversionChange",
-              "type": "void"
+              "type": "void",
+              "description": "Emitted when a conversion is added or removed, or when the order of conversions changes."
             },
             {
               "name": "arcgisPropertyChange",
@@ -2733,7 +2734,7 @@
               },
               {
                 "name": "expanded",
-                "description": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+                "description": "Describes whether the component is expanded or not. If `true`, the component is expanded and all conversions are visible.",
                 "type": "boolean"
               },
               {
@@ -2753,22 +2754,22 @@
               },
               {
                 "name": "hideCaptureButton",
-                "description": "Determines whether the capture button will be shown in the component",
+                "description": "Determines whether the capture button will be shown in the component. If `true`, the capture button will be hidden.",
                 "type": "boolean"
               },
               {
                 "name": "hideExpandButton",
-                "description": "Determines whether the expand button will be shown in the component",
+                "description": "Determines whether the expand button will be shown in the component. If `true`, the expand button will be hidden.",
                 "type": "boolean"
               },
               {
                 "name": "hideInputButton",
-                "description": "Determines whether the edit button will be shown in the component",
+                "description": "Determines whether the input coordiante button will be shown in the component. If `true`, the input button will be hidden.",
                 "type": "boolean"
               },
               {
                 "name": "hideSettingsButton",
-                "description": "Determines whether the settings button will be shown in the component",
+                "description": "Determines whether the settings button will be shown in the component. If `true`, the settings button will be hidden.",
                 "type": "boolean"
               },
               {
@@ -2783,7 +2784,7 @@
               },
               {
                 "name": "locationSymbol",
-                "description": "This symbol is used to visualize the location currently described by the component when `capture` mode\nis active.\n\nThis property should be set to an Esri JS API point symbol, typically a [Simple Marker Symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-SimpleMarkerSymbol.html)",
+                "description": "This symbol is used to visualize the location currently described by the component when `capture` mode\nis active.\n\nThis property should be set to a point symbol, typically a [Simple Marker Symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-SimpleMarkerSymbol.html).",
                 "type": "CIMSymbol | PictureMarkerSymbol | PointSymbol3D | SimpleMarkerSymbol"
               },
               {
@@ -2791,9 +2792,14 @@
                 "description": "Describes the current mode of the component.\n\n* While in `live` mode, the component will update as the cursor moves.\n* While in `capture` mode, the component will update on mouse click and display a graphic\nmarking the current location.",
                 "type": "\"capture\" | \"live\""
               },
+              {
+                "name": "multipleConversionsDisabled",
+                "description": "If this property is set to `true`, multiple conversions will be disabled, and only a single conversion will be displayed. Otherwise, multiple conversions will be shown.",
+                "type": "boolean"
+              },
               {
                 "name": "orientation",
-                "description": "Determines whether the component should expand up or down.  If set to `auto`\nthe component will be oriented based on its position in the view.",
+                "description": "Determines whether the component should expand up or down.  If set to `auto`,\nthe component will be oriented based on its position in the view.",
                 "type": "\"auto\" | \"expand-down\" | \"expand-up\""
               },
               {
@@ -2805,11 +2811,6 @@
                 "description": "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.",
                 "type": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string"
               },
-              {
-                "name": "singleConversion",
-                "description": "If this property is set to `true`, only a single conversion can be displated.  For a simpler experience with only\none conversion at a time, this property can be set to `true`.",
-                "type": "boolean"
-              },
               {
                 "name": "state",
                 "description": "The current state of the component.",
@@ -2827,14 +2828,15 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Coordinate Conversion component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
             "events": [
               {
                 "name": "arcgisConversionChange",
-                "type": "void"
+                "type": "void",
+                "description": "Emitted when a conversion is added or removed, or when the order of conversions changes."
               },
               {
                 "name": "arcgisPropertyChange",
@@ -3391,7 +3393,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Directional Pad component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               },
               {
@@ -3665,7 +3667,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Directions component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -3829,7 +3831,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -3993,7 +3995,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -4158,7 +4160,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Distance Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -4453,7 +4455,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Editor component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -4771,7 +4773,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Elevation Profile component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -5122,7 +5124,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Elevation Profile Next component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -5434,7 +5436,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Expand component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -5895,7 +5897,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Feature component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -7072,7 +7074,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Feature Table component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "LinkChartView | MapView | SceneView"
               },
               {
@@ -8049,7 +8051,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Floor Filter component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -8601,7 +8603,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Grid Controls component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -9016,7 +9018,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Home component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -9441,7 +9443,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Layer List component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -9729,7 +9731,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Legend component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -9867,7 +9869,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Line Of Sight component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -10668,7 +10670,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Link Chart Layout Switcher component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "LinkChartView"
               }
             ],
@@ -10865,7 +10867,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Locate component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -11740,7 +11742,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Measurement component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -11889,7 +11891,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Navigation Toggle component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -12155,7 +12157,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Oriented Imagery Viewer component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -12223,7 +12225,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Placement component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "LinkChartView | MapView | SceneView"
               }
             ],
@@ -12677,7 +12679,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisPopup component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Popup component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               },
               {
@@ -13002,7 +13004,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Print component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -13155,7 +13157,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Scale Bar component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -13411,7 +13413,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Scale Range Slider component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -14540,7 +14542,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Search component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -14946,7 +14948,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Shadow Cast component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               },
               {
@@ -15486,7 +15488,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Sketch component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -15701,7 +15703,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Slice component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -15922,7 +15924,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Swipe component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -16292,7 +16294,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Table List component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "LinkChartView | MapView | SceneView"
               }
             ],
@@ -16564,7 +16566,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Time Slider component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -16954,7 +16956,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Track component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],
@@ -17003,6 +17005,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-color-picker",
+              "description": "If true, hides the connectivity association color picker.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17010,6 +17013,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-style-picker",
+              "description": "If true, hides the connectivity association style picker.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17017,6 +17021,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-width-input",
+              "description": "If true, hides the connectivity association width input.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17024,6 +17029,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-color-picker",
+              "description": "If true, hides the structural attachment associations color picker.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17031,6 +17037,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-style-picker",
+              "description": "If true, hides the structural attachment associations style picker.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17038,6 +17045,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-width-input",
+              "description": "If true, hides the structural attachment associations width input.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17153,6 +17161,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-arrows-toggle",
+              "description": "If true, shows the connectivity association arrows toggle.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17160,6 +17169,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-cap-select",
+              "description": "If true, shows the connectivity association cap select.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17167,6 +17177,7 @@
             },
             {
               "name": "show-max-allowable-associations-slider",
+              "description": "If true, hides the max allowable associations slider.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17174,6 +17185,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-arrows-toggle",
+              "description": "If true, shows the structural attachment associations arrow toggle.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17181,6 +17193,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-cap-select",
+              "description": "If true, shows the structural attachment associations cap select.",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17188,7 +17201,7 @@
             },
             {
               "name": "visible-elements-connectivity-associations-settings-arrows-toggle",
-              "description": "**Deprecated**: since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead. ",
+              "description": "**Deprecated**: since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead.. ",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17196,7 +17209,7 @@
             },
             {
               "name": "visible-elements-connectivity-associations-settings-cap-select",
-              "description": "**Deprecated**: since 4.32, use showConnectivityAssociationsSettingsCapSelect instead. ",
+              "description": "**Deprecated**: since 4.32, use showConnectivityAssociationsSettingsCapSelect instead.. ",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17204,7 +17217,7 @@
             },
             {
               "name": "visible-elements-connectivity-associations-settings-color-picker",
-              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead. ",
+              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17212,7 +17225,7 @@
             },
             {
               "name": "visible-elements-connectivity-associations-settings-style-picker",
-              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead. ",
+              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17220,7 +17233,7 @@
             },
             {
               "name": "visible-elements-connectivity-associations-settings-width-input",
-              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead. ",
+              "description": "**Deprecated**: since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17228,7 +17241,7 @@
             },
             {
               "name": "visible-elements-max-allowable-associations-slider",
-              "description": "**Deprecated**: since 4.32, use showMaxAllowableAssociationsSlider instead. ",
+              "description": "**Deprecated**: since 4.32, use showMaxAllowableAssociationsSlider instead.. ",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17236,7 +17249,7 @@
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-arrows-toggle",
-              "description": "**Deprecated**: since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead. ",
+              "description": "**Deprecated**: since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead.. ",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17244,7 +17257,7 @@
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-cap-select",
-              "description": "**Deprecated**: since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead. ",
+              "description": "**Deprecated**: since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead.. ",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -17252,7 +17265,7 @@
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-color-picker",
-              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead. ",
+              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17260,7 +17273,7 @@
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-style-picker",
-              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead. ",
+              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17268,7 +17281,7 @@
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-width-input",
-              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead. ",
+              "description": "**Deprecated**: since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead.. ",
               "default": "true",
               "value": {
                 "type": "boolean"
@@ -17301,26 +17314,32 @@
               },
               {
                 "name": "hideConnectivityAssociationsSettingsColorPicker",
+                "description": "If true, hides the connectivity association color picker.",
                 "type": "boolean"
               },
               {
                 "name": "hideConnectivityAssociationsSettingsStylePicker",
+                "description": "If true, hides the connectivity association style picker.",
                 "type": "boolean"
               },
               {
                 "name": "hideConnectivityAssociationsSettingsWidthInput",
+                "description": "If true, hides the connectivity association width input.",
                 "type": "boolean"
               },
               {
                 "name": "hideStructuralAttachmentAssociationsSettingsColorPicker",
+                "description": "If true, hides the structural attachment associations color picker.",
                 "type": "boolean"
               },
               {
                 "name": "hideStructuralAttachmentAssociationsSettingsStylePicker",
+                "description": "If true, hides the structural attachment associations style picker.",
                 "type": "boolean"
               },
               {
                 "name": "hideStructuralAttachmentAssociationsSettingsWidthInput",
+                "description": "If true, hides the structural attachment associations width input.",
                 "type": "boolean"
               },
               {
@@ -17389,22 +17408,27 @@
               },
               {
                 "name": "showConnectivityAssociationsSettingsArrowsToggle",
+                "description": "If true, shows the connectivity association arrows toggle.",
                 "type": "boolean"
               },
               {
                 "name": "showConnectivityAssociationsSettingsCapSelect",
+                "description": "If true, shows the connectivity association cap select.",
                 "type": "boolean"
               },
               {
                 "name": "showMaxAllowableAssociationsSlider",
+                "description": "If true, hides the max allowable associations slider.",
                 "type": "boolean"
               },
               {
                 "name": "showStructuralAttachmentAssociationsSettingsArrowsToggle",
+                "description": "If true, shows the structural attachment associations arrow toggle.",
                 "type": "boolean"
               },
               {
                 "name": "showStructuralAttachmentAssociationsSettingsCapSelect",
+                "description": "If true, shows the structural attachment associations cap select.",
                 "type": "boolean"
               },
               {
@@ -17419,7 +17443,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Utility Network Associations component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               },
               {
@@ -17700,7 +17724,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Utility Network Trace component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -18159,7 +18183,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Utility Network Validate Topology component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -18901,7 +18925,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisVideoPlayer component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Video Player component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView"
               }
             ],
@@ -19071,7 +19095,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Weather component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -19219,7 +19243,7 @@
               },
               {
                 "name": "view",
-                "description": "The view associated with the component. \n  > **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 ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
+                "description": "The view associated with the component. \n  > **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 Zoom component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],