@arcgis/map-components 4.34.0-next.132 → 4.34.0-next.134

package/dist/docs/api.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-09-15T04:38:05",
+  "timestamp": "2025-09-17T19:21:48",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "4.34.0-next.132",
+    "version": "4.34.0-next.134",
     "typescriptVersion": "5.8.3"
   },
   "schemaVersion": "1.0.0",
@@ -131,7 +131,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -304,7 +304,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D-AreaMeasurement2DViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -427,7 +427,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -460,7 +460,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -546,7 +546,7 @@
             },
             {
               "name": "state",
-              "description": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D-AreaMeasurement2DViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -1094,6 +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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -1637,7 +1638,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -1771,7 +1772,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Attachments-AttachmentsViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -1956,7 +1957,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -2042,7 +2043,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Attachments-AttachmentsViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -2452,7 +2453,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\" | \"unsupported\"",
                 "values": [
@@ -2483,7 +2484,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the Basemap Gallery will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -2681,7 +2682,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\" | \"unsupported\"",
                 "values": [
@@ -3116,7 +3117,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -3462,7 +3463,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList-BasemapLayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -3489,7 +3490,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -3734,7 +3735,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -3953,7 +3954,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList-BasemapLayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -4360,7 +4361,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"incompatible-next-basemap\" | \"loading\" | \"ready\"",
                 "values": [
@@ -4412,7 +4413,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the component or widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -4574,7 +4575,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"incompatible-next-basemap\" | \"loading\" | \"ready\"",
                 "values": [
@@ -5327,7 +5328,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"loading\" | \"ready\"",
                 "values": [
@@ -5371,7 +5372,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -5737,7 +5738,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"loading\" | \"ready\"",
                 "values": [
@@ -6002,7 +6003,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -6012,7 +6013,13 @@
                 ]
               },
               "default": "\"organization\"",
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -6227,7 +6234,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BuildingExplorer.html#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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -6313,7 +6320,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -6722,7 +6729,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -7018,7 +7025,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList-CatalogLayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -7045,7 +7052,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -7211,7 +7218,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -7416,7 +7423,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList-CatalogLayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -7815,7 +7822,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"compass\" | \"disabled\" | \"rotation\"",
                 "values": [
@@ -7842,7 +7849,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view in which the Compass obtains and indicates camera\n[heading](https://developers.arcgis.com/javascript/latest/api-reference/esri-Camera.html#heading), using a (SceneView) or\n[rotation](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#rotation) (MapView).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -7976,7 +7983,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"compass\" | \"disabled\" | \"rotation\"",
                 "values": [
@@ -8287,7 +8294,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -8593,7 +8600,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-CoordinateConversionViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -8655,7 +8662,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -8770,7 +8777,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -8912,7 +8919,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-CoordinateConversionViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -9161,7 +9168,7 @@
             },
             {
               "kind": "field",
-              "name": "directShadowsEnabled",
+              "name": "directShadowsDisabled",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9171,7 +9178,7 @@
                 ]
               },
               "default": "false",
-              "attribute": "direct-shadows-enabled"
+              "attribute": "direct-shadows-disabled"
             },
             {
               "kind": "field",
@@ -9362,7 +9369,7 @@
               "name": "localDate",
               "description": "The calendar date in the timezone given by [utcOffset](#utcOffset).\n\nThis property should only be set once the widget and the view are initialized, for example,\nfrom within an event handler. To initialize the view with a specific date and time, set a\n[SunLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html) on the [SceneView.environment](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#environment).",
               "type": {
-                "text": "Date",
+                "text": "Date | number | string",
                 "references": [
                   {
                     "name": "Date",
@@ -9371,7 +9378,22 @@
                     "start": 0,
                     "end": 4
                   }
+                ],
+                "values": [
+                  {
+                    "type": "Date"
+                  },
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
                 ]
+              },
+              "attribute": "local-date",
+              "getterType": {
+                "text": "Date"
               }
             },
             {
@@ -9729,7 +9751,7 @@
               "fieldName": "dayPlaying"
             },
             {
-              "name": "direct-shadows-enabled",
+              "name": "direct-shadows-disabled",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -9739,7 +9761,7 @@
                 ]
               },
               "default": "false",
-              "fieldName": "directShadowsEnabled"
+              "fieldName": "directShadowsDisabled"
             },
             {
               "name": "heading-level",
@@ -9881,6 +9903,22 @@
               },
               "fieldName": "label"
             },
+            {
+              "name": "local-date",
+              "description": "The calendar date in the timezone given by [utcOffset](#utcOffset).\n\nThis property should only be set once the widget and the view are initialized, for example,\nfrom within an event handler. To initialize the view with a specific date and time, set a\n[SunLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html) on the [SceneView.environment](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#environment).",
+              "type": {
+                "text": "number | string",
+                "values": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              "fieldName": "localDate"
+            },
             {
               "name": "play-speed-multiplier",
               "description": "Controls the daytime and date animation speed.",
@@ -10385,7 +10423,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"moving\" | \"ready\"",
                 "values": [
@@ -10411,7 +10449,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view which the directional pad will control.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -10610,7 +10648,7 @@
             },
             {
               "name": "state",
-              "description": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"moving\" | \"ready\"",
                 "values": [
@@ -10899,7 +10937,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -11198,7 +11236,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Directions-DirectionsViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"initializing\" | \"ready\" | \"routing\" | \"unauthenticated\"",
                 "values": [
@@ -11314,7 +11352,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Directions.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -11449,7 +11487,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -11561,7 +11599,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Directions-DirectionsViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"initializing\" | \"ready\" | \"routing\" | \"unauthenticated\"",
                 "values": [
@@ -12091,7 +12129,7 @@
               "name": "unitOptions",
               "description": "List of available units and unit systems (imperial, metric) that are shown in the component's dropdown.\nBy default, the following units are included: `metric`, `imperial`, `inches`, `feet`, `us-feet`, `yards`, `miles`, `nautical-miles`, `meters`, `kilometers`.\nPossible [unit](#unit) values can only be a subset of this list.",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -12106,6 +12144,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -12756,7 +12795,7 @@
               "name": "unitOptions",
               "description": "List of available units and unit systems (imperial, metric) that are shown in the component's dropdown.\nBy default, the following units are included: `metric`, `imperial`, `inches`, `feet`, `us-feet`, `yards`, `miles`, `nautical-miles`, `meters`, `kilometers`.\nPossible [unit](#unit) values can only be a subset of this list.",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -12775,6 +12814,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -13181,7 +13221,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -13354,7 +13394,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D-DistanceMeasurement2DViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -13450,7 +13490,7 @@
               "name": "unitOptions",
               "description": "List of available units and unit systems (imperial, metric) for displaying the distance values.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D.html#unitOptions)",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -13465,7 +13505,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -13498,7 +13538,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -13584,7 +13624,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D-DistanceMeasurement2DViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -14017,7 +14057,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -14387,7 +14427,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor-EditorViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"add-association-create-association\" | \"add-association-select-feature\" | \"add-association-select-layer\" | \"adding-attachment\" | \"awaiting-feature-creation-info\" | \"awaiting-feature-to-create\" | \"awaiting-feature-to-update\" | \"awaiting-update-feature-candidate\" | \"creating-features\" | \"disabled\" | \"editing-attachment\" | \"editing-attributes\" | \"editing-existing-feature\" | \"editing-features\" | \"ready\" | \"viewing-selection-list\"",
                 "values": [
@@ -14501,7 +14541,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -14668,7 +14708,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -14767,7 +14807,7 @@
             },
             {
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor-EditorViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"add-association-create-association\" | \"add-association-select-feature\" | \"add-association-select-layer\" | \"adding-attachment\" | \"awaiting-feature-creation-info\" | \"awaiting-feature-to-create\" | \"awaiting-feature-to-update\" | \"awaiting-update-feature-candidate\" | \"creating-features\" | \"disabled\" | \"editing-attachment\" | \"editing-attributes\" | \"editing-existing-feature\" | \"editing-features\" | \"ready\" | \"viewing-selection-list\"",
                 "values": [
@@ -15165,7 +15205,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -15175,7 +15215,13 @@
                 ]
               },
               "default": "\"altitude\"",
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -15262,7 +15308,7 @@
               "name": "profiles",
               "description": "Collection of elevation profile lines which are to be generated and displayed in the component's chart.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile.html#profiles)",
               "type": {
-                "text": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
+                "text": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
                 "references": [
                   {
                     "name": "Collection",
@@ -15273,36 +15319,36 @@
                     "end": 10
                   },
                   {
-                    "name": "ElevationProfileLineGround",
+                    "name": "ElevationProfileElevationProfileLineGround",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
                     "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile-ElevationProfileLineGround.html",
                     "start": 11,
-                    "end": 37
+                    "end": 53
                   },
                   {
-                    "name": "ElevationProfileLineInput",
+                    "name": "ElevationProfileElevationProfileLineInput",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
                     "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile-ElevationProfileLineInput.html",
-                    "start": 40,
-                    "end": 65
+                    "start": 56,
+                    "end": 97
                   },
                   {
-                    "name": "ElevationProfileLineQuery",
+                    "name": "ElevationProfileElevationProfileLineQuery",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
                     "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile-ElevationProfileLineQuery.html",
-                    "start": 68,
-                    "end": 93
+                    "start": 100,
+                    "end": 141
                   },
                   {
                     "name": "ElevationProfileLineView",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
                     "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile-ElevationProfileLineView.html",
-                    "start": 96,
-                    "end": 120
+                    "start": 144,
+                    "end": 168
                   }
                 ]
               }
@@ -15538,7 +15584,7 @@
               "name": "unitOptions",
               "description": "List of available units and unit systems (imperial, metric) for displaying the elevation and distance values.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile.html#unitOptions)",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -15553,7 +15599,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html) or the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -15733,7 +15779,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -16358,7 +16404,7 @@
               "name": "profiles",
               "description": "Collection of elevation profile lines which are to be generated and displayed in the component's chart.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfileAnalysis.html#profiles)",
               "type": {
-                "text": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
+                "text": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
                 "references": [
                   {
                     "name": "Collection",
@@ -16369,34 +16415,34 @@
                     "end": 10
                   },
                   {
-                    "name": "ElevationProfileGroundLine",
+                    "name": "ElevationProfileLineGround",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileGroundLine.html",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileLineGround.html",
                     "start": 11,
                     "end": 37
                   },
                   {
-                    "name": "ElevationProfileInputLine",
+                    "name": "ElevationProfileLineInput",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileInputLine.html",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileLineInput.html",
                     "start": 40,
                     "end": 65
                   },
                   {
-                    "name": "ElevationProfileQueryLine",
+                    "name": "ElevationProfileLineQuery",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileQueryLine.html",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileLineQuery.html",
                     "start": 68,
                     "end": 93
                   },
                   {
-                    "name": "ElevationProfileSceneLine",
+                    "name": "ElevationProfileLineScene",
                     "package": "@arcgis/core",
                     "module": "interfaces.d.ts",
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileSceneLine.html",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-analysis-ElevationProfile-ElevationProfileLineScene.html",
                     "start": 96,
                     "end": 121
                   }
@@ -16714,7 +16760,7 @@
               "name": "unitOptionsDistance",
               "description": "List of available units and unit systems (imperial, metric) for displaying the distance values. These are the\noptions displayed in the distance unit selector in the settings popover.",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -16731,7 +16777,7 @@
               "name": "unitOptionsElevation",
               "description": "List of available units and unit systems (imperial, metric) for displaying the elevation values. These are the\noptions displayed in the elevation unit selector in the settings popover.",
               "type": {
-                "text": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+                "text": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
                 "references": [
                   {
                     "name": "Array",
@@ -16746,6 +16792,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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -17287,8 +17334,8 @@
             },
             {
               "kind": "field",
-              "name": "closeOnEsc",
-              "description": "When `true`, the Expand component will close after the Escape key is pressed when the keyboard focus is within its content.\nThis property can also be set to a function that returns a boolean, allowing for more customization for when to allow the Expand component\nto be closed from the `esc` key.",
+              "name": "closeOnEscDisabled",
+              "description": "When `true`, the Expand component will not close itself if the Escape key is pressed while its content has keyboard focus.\nThis property can also be set to a function that returns a boolean, allowing for more customization for when to allow the\nExpand component to be closed via the Escape key.",
               "type": {
                 "text": "(((event: KeyboardEvent) => boolean)) | boolean",
                 "references": [
@@ -17310,8 +17357,8 @@
                   }
                 ]
               },
-              "default": "true",
-              "attribute": "close-on-esc",
+              "default": "false",
+              "attribute": "close-on-esc-disabled",
               "docsTags": [
                 {
                   "name": "example",
@@ -17319,7 +17366,7 @@
                 },
                 {
                   "name": "example",
-                  "text": "```html\n<arcgis-expand slot=\"top-right\">\n  <arcgis-search></arcgis-search>\n</arcgis-expand>\n\n<script>\n const expandElement = document.querySelector(\"arcgis-expand\");\n const searchElement = document.querySelector(\"arcgis-search\");\n expandElement.closeOnEsc = () => {\n    // only close the expand if the search is not active\n    return searchElement.activeMenu === \"none\";\n };\n</script>\n```"
+                  "text": "```html\n<arcgis-expand slot=\"top-right\">\n  <arcgis-search></arcgis-search>\n</arcgis-expand>\n\n<script>\n const expandElement = document.querySelector(\"arcgis-expand\");\n const searchElement = document.querySelector(\"arcgis-search\");\n // don't close the expand if the search is active\n expandElement.closeOnEscDisabled = () => searchElement.activeMenu !== \"none\";\n</script>\n```"
                 }
               ]
             },
@@ -17819,7 +17866,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -17842,7 +17889,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view in which the Expand is used.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -17904,8 +17951,8 @@
               "fieldName": "autoDestroyDisabled"
             },
             {
-              "name": "close-on-esc",
-              "description": "When `true`, the Expand component will close after the Escape key is pressed when the keyboard focus is within its content.\nThis property can also be set to a function that returns a boolean, allowing for more customization for when to allow the Expand component\nto be closed from the `esc` key.",
+              "name": "close-on-esc-disabled",
+              "description": "When `true`, the Expand component will not close itself if the Escape key is pressed while its content has keyboard focus.\nThis property can also be set to a function that returns a boolean, allowing for more customization for when to allow the\nExpand component to be closed via the Escape key.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -17914,8 +17961,8 @@
                   }
                 ]
               },
-              "default": "true",
-              "fieldName": "closeOnEsc"
+              "default": "false",
+              "fieldName": "closeOnEscDisabled"
             },
             {
               "name": "collapse-icon",
@@ -18234,7 +18281,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -18358,7 +18405,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "chart-animation-disabled"
+              "attribute": "chart-animation-disabled",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "method",
@@ -18430,8 +18483,9 @@
             {
               "kind": "field",
               "name": "flowItems",
+              "description": "A collection of flow items that are used to manage drill-in navigation.",
               "type": {
-                "text": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
+                "text": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
                 "references": [
                   {
                     "name": "Collection",
@@ -18442,21 +18496,27 @@
                     "end": 10
                   },
                   {
-                    "name": "HTMLArcgisFeatureRelationshipElement",
+                    "name": "HTMLArcgisFeatureElement",
                     "module": "index.js",
                     "start": 11,
-                    "end": 47,
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature-relationship/"
+                    "end": 35,
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/"
                   },
                   {
-                    "name": "HTMLArcgisFeatureElement",
+                    "name": "HTMLArcgisFeatureRelationshipElement",
                     "module": "index.js",
-                    "start": 50,
+                    "start": 38,
                     "end": 74,
-                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/"
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature-relationship/"
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18505,6 +18565,10 @@
               "default": "null",
               "readonly": true,
               "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                },
                 {
                   "name": "see",
                   "text": "[headingLevel](#headingLevel)"
@@ -18519,7 +18583,7 @@
             {
               "kind": "field",
               "name": "headingLevel",
-              "description": "Indicates the heading level to use for the [title](#title) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
+              "description": "Indicates the heading level to use for the [heading](#heading) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
               "type": {
                 "text": "1 | 2 | 3 | 4 | 5 | 6",
                 "values": [
@@ -18590,7 +18654,93 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-content"
+              "attribute": "hide-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
+            },
+            {
+              "kind": "field",
+              "name": "hideContentAttachments",
+              "description": "Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideAttachmentsContent`](#hideAttachmentsContent) instead.",
+              "attribute": "hide-content-attachments"
+            },
+            {
+              "kind": "field",
+              "name": "hideContentExpression",
+              "description": "Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideExpressionContent`](#hideExpressionContent) instead.",
+              "attribute": "hide-content-expression"
+            },
+            {
+              "kind": "field",
+              "name": "hideContentFields",
+              "description": "Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideFieldsContent`](#hideFieldsContent) instead.",
+              "attribute": "hide-content-fields"
+            },
+            {
+              "kind": "field",
+              "name": "hideContentMedia",
+              "description": "Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideMediaContent`](#hideMediaContent) instead.",
+              "attribute": "hide-content-media"
+            },
+            {
+              "kind": "field",
+              "name": "hideContentText",
+              "description": "Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideTextContent`](#hideTextContent) instead.",
+              "attribute": "hide-content-text"
             },
             {
               "kind": "field",
@@ -18605,7 +18755,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-custom-content"
+              "attribute": "hide-custom-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18650,7 +18806,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-heading"
+              "attribute": "hide-heading",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18667,6 +18829,22 @@
               "default": "false",
               "attribute": "hide-last-edited-info"
             },
+            {
+              "kind": "field",
+              "name": "hideLastEditInfo",
+              "description": "Indicates whether to hide the title associated with the feature.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.33, use [`hideLastEditedInfo`](#hideLastEditedInfo) instead.",
+              "attribute": "hide-last-edit-info"
+            },
             {
               "kind": "field",
               "name": "hideMediaContent",
@@ -18697,6 +18875,22 @@
               "default": "false",
               "attribute": "hide-text-content"
             },
+            {
+              "kind": "field",
+              "name": "hideTitle",
+              "description": "Indicates whether to hide the title associated with the feature.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`hideHeading`](#hideHeading) instead.",
+              "attribute": "hide-title"
+            },
             {
               "kind": "field",
               "name": "icon",
@@ -18721,7 +18915,7 @@
             {
               "kind": "field",
               "name": "isFeatureFromTable",
-              "description": "Indicates whether the current FeatureViewModel's [graphic](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#graphic) resides in a non-spatial table.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#isFeatureFromTable)",
+              "description": "Indicates whether the current graphic resides in a non-spatial table.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -18732,6 +18926,12 @@
               },
               "default": "false",
               "readonly": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "docsOnlyReadonly": true
             },
             {
@@ -18809,7 +19009,13 @@
               "description": "Overwrite localized strings for this component.",
               "type": {
                 "text": "Record<string, unknown>"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "method",
@@ -19037,7 +19243,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "show-relationship-content"
+              "attribute": "show-relationship-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -19052,7 +19264,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "show-utility-network-content"
+              "attribute": "show-utility-network-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -19089,7 +19307,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"loading\" | \"ready\"",
                 "values": [
@@ -19120,7 +19338,7 @@
             {
               "kind": "field",
               "name": "timeZone",
-              "description": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n\nValue | Description |\n----- | ----------- |\nsystem  | Dates and times will be displayed in the timezone of the device or browser.\nunknown | Dates and time are not adjusted for any timezone.\nSpecified IANA timezone | Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
+              "description": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n- `system`: Dates and times will be displayed in the timezone of the device or browser.\n- `unknown`: Dates and time are not adjusted for any timezone.\n- Specified IANA timezone: Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
               "type": {
                 "text": "string",
                 "values": [
@@ -19134,6 +19352,7 @@
             {
               "kind": "method",
               "name": "updateGeometry",
+              "description": "Updates the geometry of the graphic.",
               "return": {
                 "type": {
                   "text": "Promise<void>",
@@ -19148,13 +19367,19 @@
                   ]
                 }
               },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "signature": "(): Promise<void>",
               "async": true
             },
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -19248,7 +19473,7 @@
             },
             {
               "name": "heading-level",
-              "description": "Indicates the heading level to use for the [title](#title) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
+              "description": "Indicates the heading level to use for the [heading](#heading) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
               "type": {
                 "text": "1 | 2 | 3 | 4 | 5 | 6",
                 "values": [
@@ -19309,6 +19534,81 @@
               "default": "false",
               "fieldName": "hideContent"
             },
+            {
+              "name": "hide-content-attachments",
+              "description": "Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideContentAttachments",
+              "deprecated": "since 4.34, use [`hideAttachmentsContent`](#hideAttachmentsContent) instead."
+            },
+            {
+              "name": "hide-content-expression",
+              "description": "Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideContentExpression",
+              "deprecated": "since 4.34, use [`hideExpressionContent`](#hideExpressionContent) instead."
+            },
+            {
+              "name": "hide-content-fields",
+              "description": "Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideContentFields",
+              "deprecated": "since 4.34, use [`hideFieldsContent`](#hideFieldsContent) instead."
+            },
+            {
+              "name": "hide-content-media",
+              "description": "Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideContentMedia",
+              "deprecated": "since 4.34, use [`hideMediaContent`](#hideMediaContent) instead."
+            },
+            {
+              "name": "hide-content-text",
+              "description": "Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideContentText",
+              "deprecated": "since 4.34, use [`hideTextContent`](#hideTextContent) instead."
+            },
             {
               "name": "hide-custom-content",
               "description": "This property provides the ability to hide or show [custom content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-CustomContent.html) within the component.",
@@ -19365,6 +19665,21 @@
               "default": "false",
               "fieldName": "hideHeading"
             },
+            {
+              "name": "hide-last-edit-info",
+              "description": "Indicates whether to hide the title associated with the feature.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideLastEditInfo",
+              "deprecated": "since 4.33, use [`hideLastEditedInfo`](#hideLastEditedInfo) instead."
+            },
             {
               "name": "hide-last-edited-info",
               "description": "This property provides the ability to hide or show the last edited info within the component.",
@@ -19407,6 +19722,21 @@
               "default": "false",
               "fieldName": "hideTextContent"
             },
+            {
+              "name": "hide-title",
+              "description": "Indicates whether to hide the title associated with the feature.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "hideTitle",
+              "deprecated": "since 4.34, use [`hideHeading`](#hideHeading) instead."
+            },
             {
               "name": "icon",
               "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
@@ -19523,7 +19853,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"loading\" | \"ready\"",
                 "values": [
@@ -19550,7 +19880,7 @@
             },
             {
               "name": "time-zone",
-              "description": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n\nValue | Description |\n----- | ----------- |\nsystem  | Dates and times will be displayed in the timezone of the device or browser.\nunknown | Dates and time are not adjusted for any timezone.\nSpecified IANA timezone | Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
+              "description": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n- `system`: Dates and times will be displayed in the timezone of the device or browser.\n- `unknown`: Dates and time are not adjusted for any timezone.\n- Specified IANA timezone: Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
               "type": {
                 "text": "string",
                 "values": [
@@ -19807,7 +20137,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -20019,7 +20349,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FeatureFormViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -20152,7 +20482,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -20238,7 +20568,7 @@
             },
             {
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FeatureFormViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -21550,7 +21880,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "The string value which indicates the displayed [icon](https://developers.arcgis.com/calcite-design-system/icons/).",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -22646,7 +22976,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"loaded\" | \"loading\" | \"ready\"",
                 "values": [
@@ -22877,7 +23207,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html), [LinkChartView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-LinkChartView.html), or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#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.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -23360,7 +23690,7 @@
             },
             {
               "name": "icon",
-              "description": "The string value which indicates the displayed [icon](https://developers.arcgis.com/calcite-design-system/icons/).",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -23691,7 +24021,7 @@
             },
             {
               "name": "state",
-              "description": "The state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"error\" | \"loaded\" | \"loading\" | \"ready\"",
                 "values": [
@@ -23842,7 +24172,7 @@
               "name": "arcgisPropertyChange",
               "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties.",
               "type": {
-                "text": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }"
+                "text": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }"
               }
             },
             {
@@ -24062,7 +24392,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -24280,7 +24610,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -24390,7 +24720,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -24494,7 +24824,7 @@
             },
             {
               "name": "state",
-              "description": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -24718,6 +25048,22 @@
               "signature": "(): Promise<void>",
               "async": true
             },
+            {
+              "kind": "field",
+              "name": "closed",
+              "description": "Indicates whether a component is closed. When `true`, the component will be hidden.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "deprecated": "since 4.34, use [`visible`](#visible) instead.",
+              "attribute": "closed"
+            },
             {
               "kind": "field",
               "name": "collapsed",
@@ -24861,6 +25207,12 @@
               },
               "default": "0",
               "readonly": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "docsOnlyReadonly": true
             },
             {
@@ -24876,7 +25228,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "feature-menu-open"
+              "attribute": "feature-menu-open",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -24905,7 +25263,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "feature-navigation-top"
+              "attribute": "feature-navigation-top",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -24956,6 +25320,21 @@
               "default": "20",
               "attribute": "features-per-page"
             },
+            {
+              "kind": "field",
+              "name": "featuresTitle",
+              "description": "The title of the Features component.",
+              "type": {
+                "text": "string",
+                "values": [
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              "deprecated": "since 4.34, use [`heading`](#heading) instead.",
+              "attribute": "features-title"
+            },
             {
               "kind": "field",
               "name": "featureViewModelAbilities",
@@ -25289,7 +25668,7 @@
             {
               "kind": "field",
               "name": "highlightDisabled",
-              "description": "Highlight the selected feature using one of the [HighlightOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-support-HighlightOptions.html) defined in the view's\n[highlights](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#highlights) collection.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#highlightEnabled)",
+              "description": "Indicates whether to highlight the [selected feature](#selectedFeature) in the associated\n[arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/) or [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) component.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -25298,8 +25677,14 @@
                   }
                 ]
               },
-              "default": "true",
-              "attribute": "highlight-disabled"
+              "default": "false",
+              "attribute": "highlight-disabled",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25700,7 +26085,13 @@
                   }
                 ]
               },
-              "readonly": true
+              "readonly": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25738,7 +26129,13 @@
                   }
                 ]
               },
-              "readonly": true
+              "readonly": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25825,7 +26222,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -25917,7 +26314,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#view)",
+              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\nThe Features component requires a `view` to be set if:\n- The [features](#features) have a popupTemplate containing Arcade expressions in [ExpressionInfo](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-ExpressionInfo.html) or [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html) that may use [geometry functions](https://developers.arcgis.com/arcade/function-reference/geometry_functions/) or reference the `$map` profile variable (i.e. access data from layers within a map). Alternatively, set the [`map`](#map) property.\n- Content is displayed from the popup template of an [aggregate feature](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html#isAggregate) (i.e. a [cluster](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionCluster.html) or [bin](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionBinning.html)).\n- Values from `date` and `timestamp-offset` fields should respect the view's [time zone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#timeZone).\nAlternatively, set the [`timeZone`](#timeZone) property.\n- Using the [fetchFeatures](#fetchFeatures) method or the `fetchFeatures` option in the [`open`](#open) method.\n- Using the `Zoom to` default action. If the `view` is not specified, set the [includeDefaultActions](#includeDefaultActions) property to `false` to remove this default action.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -25946,7 +26343,13 @@
                     "type": "SceneView"
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25990,6 +26393,10 @@
                 {
                   "name": "type",
                   "text": "{boolean}"
+                },
+                {
+                  "name": "since",
+                  "text": "4.34"
                 }
               ]
             }
@@ -26009,6 +26416,21 @@
               "default": "false",
               "fieldName": "autoDestroyDisabled"
             },
+            {
+              "name": "closed",
+              "description": "Indicates whether a component is closed. When `true`, the component will be hidden.",
+              "type": {
+                "text": "boolean",
+                "values": [
+                  {
+                    "type": "boolean"
+                  }
+                ]
+              },
+              "default": "false",
+              "fieldName": "closed",
+              "deprecated": "since 4.34, use [`visible`](#visible) instead."
+            },
             {
               "name": "collapsed",
               "description": "Indicates whether the component displays its content. If `true`, only the header displays.\nThis property is only honored if [`showCollapsed`](#showCollapsed) is `true`.",
@@ -26105,6 +26527,20 @@
               "default": "20",
               "fieldName": "featuresPerPage"
             },
+            {
+              "name": "features-title",
+              "description": "The title of the Features component.",
+              "type": {
+                "text": "string",
+                "values": [
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              "fieldName": "featuresTitle",
+              "deprecated": "since 4.34, use [`heading`](#heading) instead."
+            },
             {
               "name": "heading",
               "description": "The title of the Features component. This can be set to any string value no\nmatter the features that are selected. If the [selected feature](#selectedFeature)\nhas a [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html), then the title set in the\ncorresponding template is used here.",
@@ -26267,7 +26703,7 @@
             },
             {
               "name": "highlight-disabled",
-              "description": "Highlight the selected feature using one of the [HighlightOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-support-HighlightOptions.html) defined in the view's\n[highlights](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#highlights) collection.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#highlightEnabled)",
+              "description": "Indicates whether to highlight the [selected feature](#selectedFeature) in the associated\n[arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/) or [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) component.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -26276,7 +26712,7 @@
                   }
                 ]
               },
-              "default": "true",
+              "default": "false",
               "fieldName": "highlightDisabled"
             },
             {
@@ -26426,7 +26862,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -26483,7 +26919,7 @@
               "name": "arcgisPropertyChange",
               "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties.",
               "type": {
-                "text": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }"
+                "text": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }"
               }
             },
             {
@@ -26674,7 +27110,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -26891,7 +27327,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FloorFilter.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -26967,7 +27403,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -28284,7 +28720,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-support-GridControls-GridControlsViewModel.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -29060,7 +29496,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -29350,7 +29786,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Slider-SliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -29431,7 +29867,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -29640,7 +30076,7 @@
             },
             {
               "name": "state",
-              "description": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Slider-SliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -29986,7 +30422,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"going-home\" | \"ready\"",
                 "values": [
@@ -30013,7 +30449,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -30173,7 +30609,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"going-home\" | \"ready\"",
                 "values": [
@@ -30534,7 +30970,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -30919,7 +31355,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList-LayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -31035,7 +31471,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -31228,7 +31664,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -31447,7 +31883,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList-LayerListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -32135,7 +32571,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -32158,7 +32594,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -32455,7 +32891,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -32879,6 +33315,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -35461,7 +35898,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -35555,7 +35992,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#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.",
               "type": {
                 "text": "LinkChartView",
                 "references": [
@@ -35721,7 +36158,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -35975,6 +36412,7 @@
             {
               "kind": "field",
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -35984,7 +36422,13 @@
                 ]
               },
               "default": "\"gps-off\"",
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -36200,7 +36644,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the Module.",
+              "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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -36263,6 +36707,7 @@
             },
             {
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -39169,7 +39614,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -39386,7 +39831,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement-MeasurementViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -39417,7 +39862,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -39563,7 +40008,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -39711,7 +40156,7 @@
             },
             {
               "name": "state",
-              "description": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement-MeasurementViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\"",
                 "values": [
@@ -40057,6 +40502,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -40407,7 +40853,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -40698,7 +41144,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-OrientedImageryViewer.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -40803,7 +41249,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -41180,6 +41626,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.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -41323,6 +41770,10 @@
             {
               "description": "Popup",
               "url": "https://developers.arcgis.com/javascript/latest/storybook/map-components/?path=/story/arcgis-popup--demo&singleStory=true"
+            },
+            {
+              "description": "Small Map",
+              "url": "https://developers.arcgis.com/javascript/latest/storybook/map-components/?path=/story/arcgis-popup--small-map&singleStory=true"
             }
           ],
           "docsTags": [
@@ -42640,7 +43091,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -43116,7 +43567,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -43159,7 +43610,7 @@
             {
               "name": "arcgisPropertyChange",
               "type": {
-                "text": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }"
+                "text": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }"
               }
             },
             {
@@ -43820,7 +44271,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which Print will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Print-PrintViewModel.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -44474,7 +44925,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleBar-ScaleBarViewModel.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -44816,7 +45267,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -45083,7 +45534,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider-ScaleRangeSliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -45106,7 +45557,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -45208,7 +45659,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -45369,7 +45820,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider-ScaleRangeSliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -48959,7 +49410,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\" | \"searching\"",
                 "values": [
@@ -49079,7 +49530,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -49433,7 +49884,7 @@
             },
             {
               "name": "state",
-              "description": "The current state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\" | \"searching\"",
                 "values": [
@@ -50131,7 +50582,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -50141,7 +50592,13 @@
                 ]
               },
               "default": "\"measure-building-height-shadow\"",
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -50371,7 +50828,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ShadowCast.html#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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -50602,7 +51059,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -51497,7 +51954,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -51552,7 +52009,7 @@
               "name": "layer",
               "description": "The [GraphicsLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GraphicsLayer.html) associated with the Sketch widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#layer)",
               "type": {
-                "text": "GraphicsLayer",
+                "text": "GraphicsLayer | MapNotesLayer",
                 "references": [
                   {
                     "name": "GraphicsLayer",
@@ -51561,6 +52018,22 @@
                     "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GraphicsLayer.html",
                     "start": 0,
                     "end": 13
+                  },
+                  {
+                    "name": "MapNotesLayer",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-MapNotesLayer.html",
+                    "start": 16,
+                    "end": 29
+                  }
+                ],
+                "values": [
+                  {
+                    "type": "GraphicsLayer"
+                  },
+                  {
+                    "type": "MapNotesLayer"
                   }
                 ]
               }
@@ -51931,7 +52404,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The Sketch widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"active\" | \"disabled\" | \"ready\"",
                 "values": [
@@ -52128,7 +52601,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -52535,7 +53008,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -52676,7 +53149,7 @@
             },
             {
               "name": "state",
-              "description": "The Sketch widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"active\" | \"disabled\" | \"ready\"",
                 "values": [
@@ -53285,6 +53758,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -53866,7 +54340,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The current state of the Swipe.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -53930,7 +54404,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -54111,7 +54585,7 @@
             },
             {
               "name": "state",
-              "description": "The current state of the Swipe.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"ready\"",
                 "values": [
@@ -54426,7 +54900,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -54466,6 +54940,40 @@
                 "text": "(((event: TableListListItemCreatedHandlerEvent) => void))"
               }
             },
+            {
+              "kind": "field",
+              "name": "map",
+              "description": "A reference to a [map](https://developers.arcgis.com/javascript/latest/api-reference/esri-Map.html) containing the tables.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList.html#map)",
+              "type": {
+                "text": "Map | WebMap",
+                "references": [
+                  {
+                    "name": "Map",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-Map.html",
+                    "start": 0,
+                    "end": 3
+                  },
+                  {
+                    "name": "WebMap",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-WebMap.html",
+                    "start": 6,
+                    "end": 12
+                  }
+                ],
+                "values": [
+                  {
+                    "type": "Map"
+                  },
+                  {
+                    "type": "WebMap"
+                  }
+                ]
+              }
+            },
             {
               "kind": "field",
               "name": "minDragEnabledItems",
@@ -54736,7 +55244,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList-TableListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -54786,6 +55294,51 @@
                 ]
               },
               "readonly": true
+            },
+            {
+              "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.",
+              "type": {
+                "text": "LinkChartView | MapView | SceneView",
+                "references": [
+                  {
+                    "name": "LinkChartView",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-views-LinkChartView.html",
+                    "start": 0,
+                    "end": 13
+                  },
+                  {
+                    "name": "MapView",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html",
+                    "start": 16,
+                    "end": 23
+                  },
+                  {
+                    "name": "SceneView",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html",
+                    "start": 26,
+                    "end": 35
+                  }
+                ],
+                "values": [
+                  {
+                    "type": "LinkChartView"
+                  },
+                  {
+                    "type": "MapView"
+                  },
+                  {
+                    "type": "SceneView"
+                  }
+                ]
+              }
             }
           ],
           "attributes": [
@@ -54901,7 +55454,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -55120,7 +55673,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList-TableListViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"loading\" | \"ready\"",
                 "values": [
@@ -55418,7 +55971,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -55694,7 +56247,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider-TimeSliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"playing\" | \"ready\"",
                 "values": [
@@ -55899,7 +56452,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -55962,7 +56515,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -56126,7 +56679,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider-TimeSliderViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"playing\" | \"ready\"",
                 "values": [
@@ -56829,6 +57382,7 @@
             {
               "kind": "field",
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -56838,7 +57392,13 @@
                 ]
               },
               "default": "\"compass-north-circle\"",
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -57123,7 +57683,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Track-TrackViewModel.html#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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -57214,6 +57774,7 @@
             },
             {
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -57636,7 +58197,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -58008,7 +58569,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the UtilityNetworkAssociations widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkAssociations.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -58298,7 +58859,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -58963,26 +59524,10 @@
               },
               "default": "[]"
             },
-            {
-              "kind": "field",
-              "name": "gdbVersion",
-              "description": "The Geodatabase version to pass into the trace.",
-              "type": {
-                "text": "string",
-                "values": [
-                  {
-                    "type": "string"
-                  }
-                ]
-              },
-              "default": "\"sde.DEFAULT\"",
-              "deprecated": "`gdbVersion` is deprecated since version 4.31.",
-              "attribute": "gdb-version"
-            },
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -59224,7 +59769,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace-UtilityNetworkTraceViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"loading\" | \"ready\"",
                 "values": [
@@ -59273,7 +59818,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -59332,24 +59877,9 @@
               "default": "false",
               "fieldName": "enableResultArea"
             },
-            {
-              "name": "gdb-version",
-              "description": "The Geodatabase version to pass into the trace.",
-              "type": {
-                "text": "string",
-                "values": [
-                  {
-                    "type": "string"
-                  }
-                ]
-              },
-              "default": "\"sde.DEFAULT\"",
-              "fieldName": "gdbVersion",
-              "deprecated": "`gdbVersion` is deprecated since version 4.31."
-            },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -59477,7 +60007,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace-UtilityNetworkTraceViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"loading\" | \"ready\"",
                 "values": [
@@ -59824,7 +60354,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"loading\" | \"ready\"",
                 "values": [
@@ -59850,6 +60380,24 @@
               "attribute": "state",
               "reflects": true,
               "docsOnlyReadonly": true
+            },
+            {
+              "kind": "field",
+              "name": "view",
+              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#view)",
+              "type": {
+                "text": "MapView",
+                "references": [
+                  {
+                    "name": "MapView",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html",
+                    "start": 0,
+                    "end": 7
+                  }
+                ]
+              }
             }
           ],
           "attributes": [
@@ -59944,7 +60492,7 @@
             },
             {
               "name": "state",
-              "description": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"loading\" | \"ready\"",
                 "values": [
@@ -60191,6 +60739,228 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/components/utility-network-trace-analysis/components/utility-network-trace-inputs/utility-network-trace-inputs.tsx",
+      "declarations": [
+        {
+          "kind": "class",
+          "customElement": true,
+          "name": "ArcgisUtilityNetworkTraceInputs",
+          "tagName": "arcgis-utility-network-trace-inputs",
+          "description": "This is a sub-component used by the **ArcgisUtilityNetworkTraceAnalysis** component.\n\nThis sub-component takes a map view as an input.\nIt allows users to select utility networks, trace configurations, and input features for tracing.",
+          "demos": [
+            {
+              "description": "Docs",
+              "url": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-utility-network-trace-inputs/"
+            }
+          ],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
+            {
+              "name": "internal"
+            }
+          ],
+          "superclass": {
+            "name": "LitElement",
+            "package": "@arcgis/lumina"
+          },
+          "pascalCaseName": "ArcgisUtilityNetworkTraceInputs",
+          "importPath": "components/arcgis-utility-network-trace-inputs",
+          "members": [
+            {
+              "kind": "method",
+              "name": "componentOnReady",
+              "return": {
+                "type": {
+                  "text": "Promise<void>",
+                  "references": [
+                    {
+                      "module": "lib/lib.es5.d.ts",
+                      "name": "Promise",
+                      "package": "typescript",
+                      "start": 0,
+                      "end": 7
+                    }
+                  ]
+                }
+              },
+              "description": "Create a promise that resolves once component is fully loaded.",
+              "signature": "(): Promise<void>",
+              "async": true,
+              "inheritedFrom": {
+                "name": "LitElement",
+                "package": "@arcgis/lumina"
+              },
+              "docsTags": [
+                {
+                  "name": "example",
+                  "text": "```js\nconst arcgisUtilityNetworkTraceInputs = document.querySelector(\"arcgis-utility-network-trace-inputs\");\ndocument.body.append(arcgisUtilityNetworkTraceInputs);\nawait arcgisUtilityNetworkTraceInputs.componentOnReady();\nconsole.log(\"arcgis-utility-network-trace-inputs is ready to go!\");\n```"
+                }
+              ]
+            },
+            {
+              "kind": "field",
+              "name": "referenceElement",
+              "description": "By assigning the `id` attribute of the Map or Scene component to this property, you can position a child component anywhere in the DOM while still maintaining a connection to the Map or Scene.",
+              "type": {
+                "text": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+                "references": [
+                  {
+                    "name": "HTMLArcgisLinkChartElement",
+                    "module": "index.js",
+                    "start": 0,
+                    "end": 26,
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-link-chart/"
+                  },
+                  {
+                    "name": "HTMLArcgisMapElement",
+                    "module": "index.js",
+                    "start": 29,
+                    "end": 49,
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/"
+                  },
+                  {
+                    "name": "HTMLArcgisSceneElement",
+                    "module": "index.js",
+                    "start": 52,
+                    "end": 74,
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/"
+                  }
+                ],
+                "values": [
+                  {
+                    "type": "HTMLArcgisLinkChartElement"
+                  },
+                  {
+                    "type": "HTMLArcgisMapElement"
+                  },
+                  {
+                    "type": "HTMLArcgisSceneElement"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              "attribute": "reference-element",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Associate components with a Map or Scene component](https://developers.arcgis.com/javascript/latest/programming-patterns/#associate-components-with-a-map-or-scene-component)"
+                }
+              ]
+            },
+            {
+              "kind": "field",
+              "name": "selectedTraceConfiguration",
+              "type": {
+                "text": "NamedTraceConfiguration",
+                "references": [
+                  {
+                    "name": "NamedTraceConfiguration",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-networks-support-NamedTraceConfiguration.html",
+                    "start": 0,
+                    "end": 23
+                  }
+                ]
+              }
+            },
+            {
+              "kind": "field",
+              "name": "selectedUtilityNetwork",
+              "type": {
+                "text": "UtilityNetwork",
+                "references": [
+                  {
+                    "name": "UtilityNetwork",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-networks-UtilityNetwork.html",
+                    "start": 0,
+                    "end": 14
+                  }
+                ]
+              }
+            },
+            {
+              "kind": "field",
+              "name": "view",
+              "type": {
+                "text": "MapView | undefined",
+                "references": [
+                  {
+                    "name": "MapView",
+                    "package": "@arcgis/core",
+                    "module": "interfaces.d.ts",
+                    "viewUrl": "https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html",
+                    "start": 0,
+                    "end": 7
+                  }
+                ],
+                "values": [
+                  {
+                    "type": "MapView"
+                  },
+                  {
+                    "type": "undefined"
+                  }
+                ]
+              },
+              "docsTags": [
+                {
+                  "name": "required"
+                }
+              ]
+            }
+          ],
+          "attributes": [
+            {
+              "name": "reference-element",
+              "description": "By assigning the `id` attribute of the Map or Scene component to this property, you can position a child component anywhere in the DOM while still maintaining a connection to the Map or Scene.",
+              "type": {
+                "text": "string",
+                "values": [
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              "fieldName": "referenceElement"
+            }
+          ],
+          "events": [
+            {
+              "name": "arcgisTraceInputsChange",
+              "type": {
+                "text": "void"
+              }
+            },
+            {
+              "name": "arcgisUtilityNetworkChange",
+              "type": {
+                "text": "void"
+              }
+            }
+          ]
+        }
+      ],
+      "exports": [
+        {
+          "kind": "custom-element-definition",
+          "name": "arcgis-utility-network-trace-inputs",
+          "declaration": {
+            "name": "ArcgisUtilityNetworkTraceInputs",
+            "module": "src/components/utility-network-trace-analysis/components/utility-network-trace-inputs/utility-network-trace-inputs.tsx"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/components/utility-network-validate-topology/utility-network-validate-topology.tsx",
@@ -60304,7 +61074,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -60438,7 +61208,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology-UtilityNetworkValidateTopologyViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\"",
                 "values": [
@@ -60495,7 +61265,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology.html#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.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -60547,7 +61317,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon displayed in the widget's button.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -60633,7 +61403,7 @@
             },
             {
               "name": "state",
-              "description": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology-UtilityNetworkValidateTopologyViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\"",
                 "values": [
@@ -60955,7 +61725,7 @@
             {
               "kind": "field",
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -61372,7 +62142,7 @@
             },
             {
               "name": "icon",
-              "description": "Icon which represents the widget.",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -61740,6 +62510,7 @@
             {
               "kind": "field",
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -61748,7 +62519,13 @@
                   }
                 ]
               },
-              "attribute": "icon"
+              "attribute": "icon",
+              "docsTags": [
+                {
+                  "name": "see",
+                  "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -61919,7 +62696,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VersionManagement-VersionManagementViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\"",
                 "values": [
@@ -62024,6 +62801,7 @@
             },
             {
               "name": "icon",
+              "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
               "type": {
                 "text": "string",
                 "values": [
@@ -62133,7 +62911,7 @@
             },
             {
               "name": "state",
-              "description": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VersionManagement-VersionManagementViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\"",
                 "values": [
@@ -62813,7 +63591,7 @@
             {
               "kind": "field",
               "name": "state",
-              "description": "The state of the video layer.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VideoPlayer-VideoPlayerViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"can-play\" | \"data-loaded\" | \"error\" | \"not-ready\" | \"paused\" | \"playing\" | \"ready\" | \"waiting\"",
                 "values": [
@@ -63001,7 +63779,7 @@
             },
             {
               "name": "state",
-              "description": "The state of the video layer.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VideoPlayer-VideoPlayerViewModel.html#state)",
+              "description": "The current state of the component.",
               "type": {
                 "text": "\"can-play\" | \"data-loaded\" | \"error\" | \"not-ready\" | \"paused\" | \"playing\" | \"ready\" | \"waiting\"",
                 "values": [
@@ -63412,6 +64190,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.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -63917,6 +64696,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.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [