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

package/dist/docs/api.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-10-10T04:32:55",
+  "timestamp": "2025-10-12T04:31:18",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "4.34.0-next.160",
+    "version": "4.34.0-next.162",
     "typescriptVersion": "5.8.3"
   },
   "schemaVersion": "1.0.0",
@@ -427,7 +427,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -1094,7 +1094,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -2530,7 +2530,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Gallery component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -3536,7 +3536,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -4459,7 +4459,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Toggle component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -5419,7 +5419,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Bookmarks component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -6288,7 +6288,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Building Explorer component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -7106,7 +7106,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Catalog Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -7903,7 +7903,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Compass component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -8097,7 +8097,7 @@
           "customElement": true,
           "name": "ArcgisCoordinateConversion",
           "tagName": "arcgis-coordinate-conversion",
-          "description": "The CoordinateConversion component provides a way to display user cursor position either as map coordinates or\nas any of several popular coordinate notations.  Additionally, the component provides a way to convert\nuser input coordinates into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n\nSeveral common formats are included by default:\n* XY - Longitude, Latitude (WGS84)\n* MGRS - [Military Grid Reference System](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#mgrs)\n* UTM - [Universal Transverse Mercator](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#utm)\n* DD - Decimal Degrees\n* DDM - Degrees Decimal Minutes\n* DMS - Degrees Minutes Seconds\n* Basemap - X, Y in the coordinate system used by the current basemap in the units used by the basemap.\nWeb Mercator is the standard for Esri-provided basemaps.\n\nAdditional formats can be created by a developer and made available\nthrough the component",
+          "description": "The Coordinate Conversion component provides a way to display user cursor position either as map coordinates or\nas any of several popular coordinate notations.  Additionally, the component provides a way to convert\nuser input coordinates into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n\nSeveral common formats are included by default:\n* XY - Longitude, Latitude (WGS84)\n* MGRS - [Military Grid Reference System](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#mgrs)\n* UTM - [Universal Transverse Mercator](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#utm)\n* DD - Decimal Degrees\n* DDM - Degrees Decimal Minutes\n* DMS - Degrees Minutes Seconds\n* Basemap - X, Y in the coordinate system used by the current basemap in the units used by the basemap.\nWeb Mercator is the standard for Esri-provided basemaps.\n\nAdditional formats can be created by a developer and made available\nthrough the component",
           "demos": [
             {
               "description": "Docs",
@@ -8111,7 +8111,7 @@
           "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```"
             }
           ],
           "superclass": {
@@ -8199,7 +8199,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```"
                 }
               ]
             },
@@ -8227,7 +8227,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```"
                 }
               ]
             },
@@ -8255,7 +8255,7 @@
             {
               "kind": "field",
               "name": "expanded",
-              "description": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+              "description": "Describes whether the component is expanded or not. If `true`, the component is expanded and all conversions are visible.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -8274,7 +8274,7 @@
                 },
                 {
                   "name": "example",
-                  "text": "Expand the component\n```ts\ncoordinateConversionComponent.expanded = true;\n```"
+                  "text": "Expand the component\n```js\ncoordinateConversionComponent.expanded = true;\n```"
                 }
               ]
             },
@@ -8310,11 +8310,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```"
                 }
               ]
             },
@@ -8371,17 +8371,13 @@
                 {
                   "name": "type",
                   "text": "{number}"
-                },
-                {
-                  "name": "example",
-                  "text": "Coordinate conversion heading will render as an <h2>\n```ts\ncoordinateConversionComponent.headingLevel = 2;\n```ts"
                 }
               ]
             },
             {
               "kind": "field",
               "name": "hideCaptureButton",
-              "description": "Determines whether the capture button will be shown in the component",
+              "description": "Determines whether the capture button will be shown in the component. If `true`, the capture button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -8400,14 +8396,14 @@
                 },
                 {
                   "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```"
                 }
               ]
             },
             {
               "kind": "field",
               "name": "hideExpandButton",
-              "description": "Determines whether the expand button will be shown in the component",
+              "description": "Determines whether the expand button will be shown in the component. If `true`, the expand button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -8426,14 +8422,14 @@
                 },
                 {
                   "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```"
                 }
               ]
             },
             {
               "kind": "field",
               "name": "hideInputButton",
-              "description": "Determines whether the edit button will be shown in the component",
+              "description": "Determines whether the input coordiante button will be shown in the component. If `true`, the input button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -8452,14 +8448,14 @@
                 },
                 {
                   "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```"
                 }
               ]
             },
             {
               "kind": "field",
               "name": "hideSettingsButton",
-              "description": "Determines whether the settings button will be shown in the component",
+              "description": "Determines whether the settings button will be shown in the component. If `true`, the settings button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -8478,7 +8474,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```"
                 }
               ]
             },
@@ -8515,7 +8511,7 @@
             {
               "kind": "field",
               "name": "locationSymbol",
-              "description": "This symbol is used to visualize the location currently described by the component when `capture` mode\nis active.\n\nThis property should be set to an Esri JS API point symbol, typically a [Simple Marker Symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-SimpleMarkerSymbol.html)",
+              "description": "This symbol is used to visualize the location currently described by the component when `capture` mode\nis active.\n\nThis property should be set to a point symbol, typically a [Simple Marker Symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-SimpleMarkerSymbol.html).",
               "type": {
                 "text": "CIMSymbol | PictureMarkerSymbol | PointSymbol3D | SimpleMarkerSymbol",
                 "references": [
@@ -8574,7 +8570,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```"
                 }
               ]
             },
@@ -8605,14 +8601,36 @@
                 },
                 {
                   "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```"
+                }
+              ]
+            },
+            {
+              "kind": "field",
+              "name": "multipleConversionsDisabled",
+              "description": "If this property is set to `true`, multiple conversions will be disabled, and only a single conversion will be displayed. Otherwise, multiple conversions will be shown.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "attribute": "multiple-conversions-disabled",
+              "reflects": true,
+              "docsTags": [
+                {
+                  "name": "type",
+                  "text": "{boolean}"
                 }
               ]
             },
             {
               "kind": "field",
               "name": "orientation",
-              "description": "Determines whether the component should expand up or down.  If set to `auto`\nthe component will be oriented based on its position in the view.",
+              "description": "Determines whether the component should expand up or down.  If set to `auto`,\nthe component will be oriented based on its position in the view.",
               "type": {
                 "text": "\"auto\" | \"expand-down\" | \"expand-up\"",
                 "values": [
@@ -8812,28 +8830,6 @@
               "signature": "(coordinate: string, format: Format): Promise<__esri.Point | nullish>",
               "async": true
             },
-            {
-              "kind": "field",
-              "name": "singleConversion",
-              "description": "If this property is set to `true`, only a single conversion can be displated.  For a simpler experience with only\none conversion at a time, this property can be set to `true`.",
-              "type": {
-                "text": "boolean",
-                "values": [
-                  {
-                    "type": "boolean"
-                  }
-                ]
-              },
-              "default": "false",
-              "attribute": "single-conversion",
-              "reflects": true,
-              "docsTags": [
-                {
-                  "name": "type",
-                  "text": "{boolean}"
-                }
-              ]
-            },
             {
               "kind": "field",
               "name": "state",
@@ -8920,7 +8916,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Coordinate Conversion component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -8969,7 +8965,7 @@
             },
             {
               "name": "expanded",
-              "description": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+              "description": "Describes whether the component is expanded or not. If `true`, the component is expanded and all conversions are visible.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9018,7 +9014,7 @@
             },
             {
               "name": "hide-capture-button",
-              "description": "Determines whether the capture button will be shown in the component",
+              "description": "Determines whether the capture button will be shown in the component. If `true`, the capture button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9032,7 +9028,7 @@
             },
             {
               "name": "hide-expand-button",
-              "description": "Determines whether the expand button will be shown in the component",
+              "description": "Determines whether the expand button will be shown in the component. If `true`, the expand button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9046,7 +9042,7 @@
             },
             {
               "name": "hide-input-button",
-              "description": "Determines whether the edit button will be shown in the component",
+              "description": "Determines whether the input coordiante button will be shown in the component. If `true`, the input button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9060,7 +9056,7 @@
             },
             {
               "name": "hide-settings-button",
-              "description": "Determines whether the settings button will be shown in the component",
+              "description": "Determines whether the settings button will be shown in the component. If `true`, the settings button will be hidden.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9119,9 +9115,23 @@
               "default": "\"live\"",
               "fieldName": "mode"
             },
+            {
+              "name": "multiple-conversions-disabled",
+              "description": "If this property is set to `true`, multiple conversions will be disabled, and only a single conversion will be displayed. Otherwise, multiple conversions will be shown.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "multipleConversionsDisabled"
+            },
             {
               "name": "orientation",
-              "description": "Determines whether the component should expand up or down.  If set to `auto`\nthe component will be oriented based on its position in the view.",
+              "description": "Determines whether the component should expand up or down.  If set to `auto`,\nthe component will be oriented based on its position in the view.",
               "type": {
                 "text": "\"auto\" | \"expand-down\" | \"expand-up\"",
                 "values": [
@@ -9201,20 +9211,6 @@
               },
               "fieldName": "referenceElement"
             },
-            {
-              "name": "single-conversion",
-              "description": "If this property is set to `true`, only a single conversion can be displated.  For a simpler experience with only\none conversion at a time, this property can be set to `true`.",
-              "type": {
-                "text": "boolean",
-                "values": [
-                  {
-                    "type": "boolean"
-                  }
-                ]
-              },
-              "default": "false",
-              "fieldName": "singleConversion"
-            },
             {
               "name": "state",
               "description": "The current state of the component.",
@@ -9275,9 +9271,16 @@
           "events": [
             {
               "name": "arcgisConversionChange",
+              "description": "Emitted when a conversion is added or removed, or when the order of conversions changes.",
               "type": {
                 "text": "void"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisPropertyChange",
@@ -10721,7 +10724,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directional Pad component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -11624,7 +11627,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directions component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -12416,7 +12419,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -13086,7 +13089,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -13777,7 +13780,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Distance Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -14826,7 +14829,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Editor component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -15896,7 +15899,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -17096,7 +17099,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile Next component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -18197,7 +18200,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Expand component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -19694,7 +19697,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -23533,7 +23536,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature Table component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -27640,7 +27643,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Floor Filter component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -29033,7 +29036,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Grid Controls component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -30762,7 +30765,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Home component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -31784,7 +31787,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -32908,7 +32911,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Legend component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -33629,7 +33632,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Line Of Sight component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -36477,7 +36480,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Link Chart Layout Switcher component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView",
                 "references": [
@@ -37129,7 +37132,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Locate component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -40530,7 +40533,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Measurement component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -41170,7 +41173,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Navigation Toggle component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -41812,7 +41815,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Oriented Imagery Viewer component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -42294,7 +42297,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Placement component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -43782,7 +43785,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPopup component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Popup component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -44949,7 +44952,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Print component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -45603,7 +45606,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Bar component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -46250,7 +46253,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Range Slider component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -50373,7 +50376,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Search component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -51676,7 +51679,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Shadow Cast component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -53449,7 +53452,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Sketch component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -54606,7 +54609,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Slice component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -55252,7 +55255,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Swipe component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -56146,7 +56149,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Table List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -57300,7 +57303,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Time Slider component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -58572,7 +58575,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Track component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -59002,6 +59005,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsColorPicker",
+              "description": "If true, hides the connectivity association color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59016,6 +59020,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsStylePicker",
+              "description": "If true, hides the connectivity association style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59030,6 +59035,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsWidthInput",
+              "description": "If true, hides the connectivity association width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59044,6 +59050,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsColorPicker",
+              "description": "If true, hides the structural attachment associations color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59058,6 +59065,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsStylePicker",
+              "description": "If true, hides the structural attachment associations style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59072,6 +59080,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsWidthInput",
+              "description": "If true, hides the structural attachment associations width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59352,6 +59361,7 @@
             {
               "kind": "field",
               "name": "showConnectivityAssociationsSettingsArrowsToggle",
+              "description": "If true, shows the connectivity association arrows toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59366,6 +59376,7 @@
             {
               "kind": "field",
               "name": "showConnectivityAssociationsSettingsCapSelect",
+              "description": "If true, shows the connectivity association cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59380,6 +59391,7 @@
             {
               "kind": "field",
               "name": "showMaxAllowableAssociationsSlider",
+              "description": "If true, hides the max allowable associations slider.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59394,6 +59406,7 @@
             {
               "kind": "field",
               "name": "showStructuralAttachmentAssociationsSettingsArrowsToggle",
+              "description": "If true, shows the structural attachment associations arrow toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59408,6 +59421,7 @@
             {
               "kind": "field",
               "name": "showStructuralAttachmentAssociationsSettingsCapSelect",
+              "description": "If true, shows the structural attachment associations cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59458,7 +59472,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Associations component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -59485,7 +59499,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead",
+              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead.",
               "attribute": "visible-elements-connectivity-associations-settings-arrows-toggle"
             },
             {
@@ -59500,7 +59514,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead",
+              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead.",
               "attribute": "visible-elements-connectivity-associations-settings-cap-select"
             },
             {
@@ -59515,7 +59529,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead.",
               "attribute": "visible-elements-connectivity-associations-settings-color-picker"
             },
             {
@@ -59530,7 +59544,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead.",
               "attribute": "visible-elements-connectivity-associations-settings-style-picker"
             },
             {
@@ -59545,7 +59559,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead.",
               "attribute": "visible-elements-connectivity-associations-settings-width-input"
             },
             {
@@ -59560,7 +59574,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead",
+              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead.",
               "attribute": "visible-elements-max-allowable-associations-slider"
             },
             {
@@ -59575,7 +59589,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead",
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-arrows-toggle"
             },
             {
@@ -59590,7 +59604,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead",
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-cap-select"
             },
             {
@@ -59605,7 +59619,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-color-picker"
             },
             {
@@ -59620,7 +59634,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-style-picker"
             },
             {
@@ -59635,7 +59649,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-width-input"
             }
           ],
@@ -59670,6 +59684,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-color-picker",
+              "description": "If true, hides the connectivity association color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59683,6 +59698,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-style-picker",
+              "description": "If true, hides the connectivity association style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59696,6 +59712,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-width-input",
+              "description": "If true, hides the connectivity association width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59709,6 +59726,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-color-picker",
+              "description": "If true, hides the structural attachment associations color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59722,6 +59740,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-style-picker",
+              "description": "If true, hides the structural attachment associations style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59735,6 +59754,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-width-input",
+              "description": "If true, hides the structural attachment associations width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59957,6 +59977,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-arrows-toggle",
+              "description": "If true, shows the connectivity association arrows toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59970,6 +59991,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-cap-select",
+              "description": "If true, shows the connectivity association cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59983,6 +60005,7 @@
             },
             {
               "name": "show-max-allowable-associations-slider",
+              "description": "If true, hides the max allowable associations slider.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59996,6 +60019,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-arrows-toggle",
+              "description": "If true, shows the structural attachment associations arrow toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -60009,6 +60033,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-cap-select",
+              "description": "If true, shows the structural attachment associations cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -60032,7 +60057,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsArrowsToggle",
-              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead"
+              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-cap-select",
@@ -60046,7 +60071,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsCapSelect",
-              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead"
+              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-color-picker",
@@ -60060,7 +60085,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsColorPicker",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-style-picker",
@@ -60074,7 +60099,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsStylePicker",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-width-input",
@@ -60088,7 +60113,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsWidthInput",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead."
             },
             {
               "name": "visible-elements-max-allowable-associations-slider",
@@ -60102,7 +60127,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsMaxAllowableAssociationsSlider",
-              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead"
+              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-arrows-toggle",
@@ -60116,7 +60141,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsArrowsToggle",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead"
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-cap-select",
@@ -60130,7 +60155,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsCapSelect",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead"
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-color-picker",
@@ -60144,7 +60169,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsColorPicker",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-style-picker",
@@ -60158,7 +60183,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsStylePicker",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-width-input",
@@ -60172,7 +60197,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsWidthInput",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead."
             }
           ],
           "events": [
@@ -60707,7 +60732,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Trace component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -61032,10 +61057,6 @@
             {
               "description": "Docs",
               "url": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-utility-network-trace-analysis/"
-            },
-            {
-              "description": "Utility Network Trace Analysis",
-              "url": "https://developers.arcgis.com/javascript/latest/storybook/map-components/?path=/story/arcgis-utility-network-trace-analysis--demo&singleStory=true"
             }
           ],
           "docsTags": [
@@ -62363,7 +62384,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Validate Topology component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -64776,7 +64797,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisVideoPlayer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Video Player component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -65348,7 +65369,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Weather component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -65854,7 +65875,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Zoom component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [