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

package/dist/docs/docs.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-10-10T04:32:55",
+  "timestamp": "2025-10-11T04:31:22",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "4.34.0-next.160",
+    "version": "4.34.0-next.161",
     "typescriptVersion": "5.8.3"
   },
   "components": [
@@ -386,7 +386,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -910,7 +910,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -2150,7 +2150,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -3219,7 +3219,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -3745,7 +3745,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -4689,7 +4689,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -5322,7 +5322,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -6140,7 +6140,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -6632,7 +6632,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -6767,11 +6767,11 @@
       "overview": "",
       "readme": "",
       "usage": {},
-      "docs": "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",
+      "docs": "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",
       "docsTags": [
         {
           "name": "example",
-          "text": "```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+          "text": "```html\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion slot=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
         },
         {
           "name": "superclass",
@@ -6834,7 +6834,7 @@
             },
             {
               "name": "example",
-              "text": "Conversions can be set with an array of strings where each string is a format's name\n```ts\ncoordinateConversionComponent.conversions = [\"mgrs\"];\n```"
+              "text": "Conversions can be set with an array of strings where each string is a format's name\n```js\ncoordinateConversionComponent.conversions = [\"mgrs\"];\n```"
             }
           ],
           "values": [],
@@ -6865,7 +6865,7 @@
             },
             {
               "name": "example",
-              "text": "Set the current location\n```ts\ncoordinateConversionComponent.currentLocation = { x: 77.0369, y: 38.9072, spatialReference: { wkid: 4326 } };\n```"
+              "text": "Set the current location\n```js\ncoordinateConversionComponent.currentLocation = { x: 77.0369, y: 38.9072, spatialReference: { wkid: 4326 } };\n```"
             }
           ],
           "values": [],
@@ -6883,7 +6883,7 @@
           "mutable": true,
           "attr": "expanded",
           "reflectToAttr": true,
-          "docs": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+          "docs": "Describes whether the component is expanded or not. If `true`, the component is expanded and all conversions are visible.",
           "docsTags": [
             {
               "name": "type",
@@ -6891,7 +6891,7 @@
             },
             {
               "name": "example",
-              "text": "Expand the component\n```ts\ncoordinateConversionComponent.expanded = true;\n```"
+              "text": "Expand the component\n```js\ncoordinateConversionComponent.expanded = true;\n```"
             }
           ],
           "default": "false",
@@ -6932,11 +6932,11 @@
             },
             {
               "name": "example",
-              "text": "Only show the \"xy\" format\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name !== \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
+              "text": "Only show the \"xy\" format\n```js\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name !== \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
             },
             {
               "name": "example",
-              "text": "Show every format except \"xy\"\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name === \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
+              "text": "Show every format except \"xy\"\n```js\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name === \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
             }
           ],
           "values": [],
@@ -6980,10 +6980,6 @@
             {
               "name": "type",
               "text": "{number}"
-            },
-            {
-              "name": "example",
-              "text": "Coordinate conversion heading will render as an <h2>\n```ts\ncoordinateConversionComponent.headingLevel = 2;\n```ts"
             }
           ],
           "default": "4",
@@ -7027,7 +7023,7 @@
           "mutable": true,
           "attr": "hide-capture-button",
           "reflectToAttr": true,
-          "docs": "Determines whether the capture button will be shown in the component",
+          "docs": "Determines whether the capture button will be shown in the component. If `true`, the capture button will be hidden.",
           "docsTags": [
             {
               "name": "type",
@@ -7035,7 +7031,7 @@
             },
             {
               "name": "example",
-              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-capture-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+              "text": "Hide the capture button\n```html\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-capture-button slot=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
             }
           ],
           "default": "false",
@@ -7058,7 +7054,7 @@
           "mutable": true,
           "attr": "hide-expand-button",
           "reflectToAttr": true,
-          "docs": "Determines whether the expand button will be shown in the component",
+          "docs": "Determines whether the expand button will be shown in the component. If `true`, the expand button will be hidden.",
           "docsTags": [
             {
               "name": "type",
@@ -7066,7 +7062,7 @@
             },
             {
               "name": "example",
-              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-expand-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+              "text": "Hide the capture button\n```html\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-expand-button slot=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
             }
           ],
           "default": "false",
@@ -7089,7 +7085,7 @@
           "mutable": true,
           "attr": "hide-input-button",
           "reflectToAttr": true,
-          "docs": "Determines whether the edit button will be shown in the component",
+          "docs": "Determines whether the input coordiante button will be shown in the component. If `true`, the input button will be hidden.",
           "docsTags": [
             {
               "name": "type",
@@ -7097,7 +7093,7 @@
             },
             {
               "name": "example",
-              "text": "Hide the edit button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-edit-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+              "text": "Hide the input button\n```html\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-input-button slot=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
             }
           ],
           "default": "false",
@@ -7120,7 +7116,7 @@
           "mutable": true,
           "attr": "hide-settings-button",
           "reflectToAttr": true,
-          "docs": "Determines whether the settings button will be shown in the component",
+          "docs": "Determines whether the settings button will be shown in the component. If `true`, the settings button will be hidden.",
           "docsTags": [
             {
               "name": "type",
@@ -7128,7 +7124,7 @@
             },
             {
               "name": "example",
-              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-settings-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+              "text": "Hide the capture button\n```html\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-settings-button slot=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
             }
           ],
           "default": "false",
@@ -7215,7 +7211,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "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).",
           "docsTags": [
             {
               "name": "type",
@@ -7223,7 +7219,7 @@
             },
             {
               "name": "example",
-              "text": "Set the location symbol to be an 'x'\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.locationSymbol = { type: \"simple-marker\", style: \"x\" };\n```"
+              "text": "Set the location symbol to be an 'x'\n```js\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.locationSymbol = { type: \"simple-marker\", style: \"x\" };\n```"
             }
           ],
           "values": [
@@ -7262,7 +7258,7 @@
             },
             {
               "name": "example",
-              "text": "Programmatically set the component to capture mode\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.mode = \"capture\";\n```"
+              "text": "Programmatically set the component to capture mode\n```js\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.mode = \"capture\";\n```"
             }
           ],
           "default": "\"live\"",
@@ -7279,6 +7275,33 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "multipleConversionsDisabled",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "multiple-conversions-disabled",
+          "reflectToAttr": true,
+          "docs": "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.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            }
+          ],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "orientation",
           "type": "\"auto\" | \"expand-down\" | \"expand-up\"",
@@ -7290,7 +7313,7 @@
           "mutable": true,
           "attr": "orientation",
           "reflectToAttr": true,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [
             {
               "name": "type",
@@ -7421,33 +7444,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "singleConversion",
-          "type": "boolean",
-          "complexType": {
-            "original": "boolean",
-            "resolved": "boolean",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "single-conversion",
-          "reflectToAttr": true,
-          "docs": "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`.",
-          "docsTags": [
-            {
-              "name": "type",
-              "text": "{boolean}"
-            }
-          ],
-          "default": "false",
-          "values": [
-            {
-              "type": "boolean"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
         {
           "name": "state",
           "type": "\"disabled\" | \"loading\" | \"ready\"",
@@ -7572,7 +7568,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -7723,8 +7719,13 @@
           },
           "cancelable": true,
           "composed": true,
-          "docs": "",
-          "docsTags": []
+          "docs": "Emitted when a conversion is added or removed, or when the order of conversions changes.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisPropertyChange",
@@ -8955,7 +8956,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -9690,7 +9691,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -10292,7 +10293,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -10846,7 +10847,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [
             {
               "name": "inheritedFrom",
@@ -11389,7 +11390,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -12234,7 +12235,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -13314,7 +13315,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -14327,7 +14328,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -15162,7 +15163,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -16394,7 +16395,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -19806,7 +19807,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -23286,7 +23287,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -24638,7 +24639,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -25788,7 +25789,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -26888,7 +26889,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -27790,7 +27791,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -28187,7 +28188,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -31013,7 +31014,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -31571,7 +31572,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -34854,7 +34855,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -35298,7 +35299,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -35932,7 +35933,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -36193,7 +36194,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -37439,7 +37440,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -38661,7 +38662,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -39087,7 +39088,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -39705,7 +39706,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -43562,7 +43563,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -44741,7 +44742,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -46252,7 +46253,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -47151,7 +47152,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -47728,7 +47729,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -48627,7 +48628,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -49381,7 +49382,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -50545,7 +50546,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {
@@ -50836,7 +50837,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-color-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association color picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50858,7 +50859,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-style-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association style picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50880,7 +50881,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-width-input",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association width input.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50902,7 +50903,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-color-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations color picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50924,7 +50925,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-style-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations style picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50946,7 +50947,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-width-input",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations width input.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51317,7 +51318,7 @@
           "mutable": true,
           "attr": "show-connectivity-associations-settings-arrows-toggle",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the connectivity association arrows toggle.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51339,7 +51340,7 @@
           "mutable": true,
           "attr": "show-connectivity-associations-settings-cap-select",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the connectivity association cap select.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51361,7 +51362,7 @@
           "mutable": true,
           "attr": "show-max-allowable-associations-slider",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the max allowable associations slider.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51383,7 +51384,7 @@
           "mutable": true,
           "attr": "show-structural-attachment-associations-settings-arrows-toggle",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the structural attachment associations arrow toggle.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51405,7 +51406,7 @@
           "mutable": true,
           "attr": "show-structural-attachment-associations-settings-cap-select",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the structural attachment associations cap select.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -51476,7 +51477,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -51496,7 +51497,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead",
+          "deprecation": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead.",
           "values": [
             {
               "type": "boolean"
@@ -51519,7 +51520,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead",
+          "deprecation": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead.",
           "values": [
             {
               "type": "boolean"
@@ -51542,7 +51543,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51565,7 +51566,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51588,7 +51589,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead.",
           "values": [
             {
               "type": "boolean"
@@ -51611,7 +51612,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showMaxAllowableAssociationsSlider instead",
+          "deprecation": "since 4.32, use showMaxAllowableAssociationsSlider instead.",
           "values": [
             {
               "type": "boolean"
@@ -51634,7 +51635,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead",
+          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead.",
           "values": [
             {
               "type": "boolean"
@@ -51657,7 +51658,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead",
+          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead.",
           "values": [
             {
               "type": "boolean"
@@ -51680,7 +51681,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51703,7 +51704,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51726,7 +51727,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead.",
           "values": [
             {
               "type": "boolean"
@@ -52327,7 +52328,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -53915,7 +53916,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -56033,7 +56034,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "default": "null",
           "values": [],
@@ -56490,7 +56491,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -56878,7 +56879,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [],
           "values": [
             {