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

package/dist/docs/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://raw.githubusercontent.com/JetBrains/web-types/master/schema/web-types.json",
   "name": "@arcgis/map-components",
-  "version": "4.34.0-next.132",
+  "version": "4.34.0-next.134",
   "description-markup": "markdown",
   "contributions": {
     "html": {
@@ -21,7 +21,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).",
               "default": "\"measure-area\"",
               "value": {
                 "type": "string"
@@ -60,7 +60,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -117,7 +117,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": "string"
               },
               {
@@ -141,7 +141,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": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\""
               },
               {
@@ -156,7 +156,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -323,6 +323,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -423,7 +424,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).",
               "default": "\"attachment\"",
               "value": {
                 "type": "string"
@@ -462,7 +463,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.",
               "default": "\"ready\"",
               "value": {
                 "type": [
@@ -546,7 +547,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": "string"
               },
               {
@@ -565,7 +566,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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
@@ -673,7 +674,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -750,12 +751,12 @@
               },
               {
                 "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": "\"disabled\" | \"loading\" | \"ready\" | \"unsupported\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -886,7 +887,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).",
               "default": "\"layers\"",
               "value": {
                 "type": "string"
@@ -996,7 +997,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -1134,7 +1135,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": "string"
               },
               {
@@ -1212,12 +1213,12 @@
               },
               {
                 "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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -1319,7 +1320,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -1391,12 +1392,12 @@
               },
               {
                 "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": "\"disabled\" | \"incompatible-next-basemap\" | \"loading\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -1595,7 +1596,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.",
               "default": "\"ready\"",
               "value": {
                 "type": [
@@ -1763,7 +1764,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": "\"loading\" | \"ready\""
               },
               {
@@ -1773,7 +1774,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -1845,7 +1846,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).",
               "default": "\"organization\"",
               "value": {
                 "type": "string"
@@ -1934,7 +1935,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": "string"
               },
               {
@@ -1973,7 +1974,7 @@
               },
               {
                 "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": "SceneView"
               }
             ],
@@ -2060,7 +2061,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).",
               "default": "\"catalog-dataset\"",
               "value": {
                 "type": "string"
@@ -2162,7 +2163,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -2263,7 +2264,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": "string"
               },
               {
@@ -2326,12 +2327,12 @@
               },
               {
                 "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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -2417,7 +2418,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -2483,12 +2484,12 @@
               },
               {
                 "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": "\"compass\" | \"disabled\" | \"rotation\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -2557,7 +2558,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).",
               "default": "\"coordinate-system\"",
               "value": {
                 "type": "string"
@@ -2627,7 +2628,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -2719,7 +2720,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": "string"
               },
               {
@@ -2758,7 +2759,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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
@@ -2773,7 +2774,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -2836,7 +2837,7 @@
               }
             },
             {
-              "name": "direct-shadows-enabled",
+              "name": "direct-shadows-disabled",
               "default": "false",
               "value": {
                 "type": "boolean"
@@ -2914,6 +2915,16 @@
                 "type": "string"
               }
             },
+            {
+              "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).",
+              "value": {
+                "type": [
+                  "number",
+                  "string"
+                ]
+              }
+            },
             {
               "name": "play-speed-multiplier",
               "description": "Controls the daytime and date animation speed.",
@@ -3030,7 +3041,7 @@
                 "type": "boolean"
               },
               {
-                "name": "directShadowsEnabled",
+                "name": "directShadowsDisabled",
                 "type": "boolean"
               },
               {
@@ -3079,7 +3090,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": "Date"
+                "type": "Date | number | string"
               },
               {
                 "name": "playingState",
@@ -3233,7 +3244,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.",
               "value": {
                 "type": [
                   "\"disabled\"",
@@ -3320,12 +3331,12 @@
               },
               {
                 "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": "\"disabled\" | \"moving\" | \"ready\""
               },
               {
                 "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": "MapView"
               },
               {
@@ -3399,7 +3410,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).",
               "default": "\"right\"",
               "value": {
                 "type": "string"
@@ -3452,7 +3463,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -3542,7 +3553,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": "string"
               },
               {
@@ -3585,7 +3596,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": "\"disabled\" | \"error\" | \"initializing\" | \"ready\" | \"routing\" | \"unauthenticated\""
               },
               {
@@ -3599,7 +3610,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -3759,10 +3770,11 @@
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "SceneView"
               }
             ],
@@ -3922,10 +3934,11 @@
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "SceneView"
               }
             ],
@@ -3958,7 +3971,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).",
               "default": "\"measure-line\"",
               "value": {
                 "type": "string"
@@ -3997,7 +4010,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -4051,7 +4064,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": "string"
               },
               {
@@ -4075,7 +4088,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": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\""
               },
               {
@@ -4086,11 +4099,11 @@
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "MapView"
               }
             ],
@@ -4187,7 +4200,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).",
               "default": "\"pencil\"",
               "value": {
                 "type": "string"
@@ -4233,7 +4246,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.",
               "value": {
                 "type": [
                   "\"add-association-create-association\"",
@@ -4329,7 +4342,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": "string"
               },
               {
@@ -4367,7 +4380,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": "\"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\""
               },
               {
@@ -4382,7 +4395,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -4496,7 +4509,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).",
               "default": "\"altitude\"",
               "value": {
                 "type": "string"
@@ -4646,7 +4659,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": "string"
               },
               {
@@ -4666,7 +4679,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": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>"
+                "type": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>"
               },
               {
                 "name": "progress",
@@ -4696,11 +4709,11 @@
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -5002,7 +5015,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": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>"
+                "type": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>"
               },
               {
                 "name": "progress",
@@ -5037,15 +5050,16 @@
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">"
+                "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">"
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -5085,9 +5099,9 @@
               }
             },
             {
-              "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.",
-              "default": "true",
+              "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.",
+              "default": "false",
               "value": {
                 "type": "boolean"
               }
@@ -5237,7 +5251,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -5272,8 +5286,8 @@
                 "type": "boolean"
               },
               {
-                "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": "(((event: KeyboardEvent) => boolean)) | boolean"
               },
               {
@@ -5352,12 +5366,12 @@
               },
               {
                 "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": "\"disabled\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -5377,7 +5391,7 @@
         },
         {
           "name": "arcgis-feature",
-          "description": "The Feature component displays a graphic according to its [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\nThis component is useful in instances where you want to display information about a feature but without\nthe use of a [Popup](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Popup.html).\n\nIf wanting to show a feature's content with [actions](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#actions), [related](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html), or [clustering](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionCluster.html#popupTemplate), etc., then use the [arcgis-features](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-features/) component.\n\nWhen Arcade expressions that use `$map` or [geometry functions](https://developers.arcgis.com/arcade/function-reference/geometry_functions/) are defined in any popup template content or as expression elements,\nthe [map](#map) and [spatialReference](#spatialReference) properties need to be defined in the Feature component.\n--\n\n### Events\n- **arcgisPropertyChange** - Emitted when the value of a property is changed. Use this to listen to changes to properties.\n- **arcgisReady** - Emitted when the component associated with a map or scene view is ready to be interacted with.\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.\n- `destroy(): Promise<void>` - Permanently destroy the component.\n- `nextMedia(contentElementIndex: number): Promise<void>` - Paginates to the next [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info.\n- `previousMedia(contentElementIndex: number): Promise<void>` - Paginates to the previous [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info in the specified\n[media](esri-popup-content-MediaContent.html) content element.\n- `setActiveMedia(contentElementIndex: number, mediaInfoIndex: number): Promise<void>` - Paginates to a specified [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info object. For example,\nyou may have [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) content which contains\nmultiple `mediaInfos`. This method allows you to specify the index of the `mediaInfos`\nyou wish to display.\n\n::: esri-md class=\"warning\"\nPrior to   version 4.17, this method was named `goToMedia`.\n:::\n- `updateGeometry(): Promise<void>`",
+          "description": "The Feature component displays a graphic according to its [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\nThis component is useful in instances where you want to display information about a feature but without\nthe use of a [Popup](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Popup.html).\n\nIf wanting to show a feature's content with [actions](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#actions), [related](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html), or [clustering](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionCluster.html#popupTemplate), etc., then use the [arcgis-features](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-features/) component.\n\nWhen Arcade expressions that use `$map` or [geometry functions](https://developers.arcgis.com/arcade/function-reference/geometry_functions/) are defined in any popup template content or as expression elements,\nthe [map](#map) and [spatialReference](#spatialReference) properties need to be defined in the Feature component.\n--\n\n### Events\n- **arcgisPropertyChange** - Emitted when the value of a property is changed. Use this to listen to changes to properties.\n- **arcgisReady** - Emitted when the component associated with a map or scene view is ready to be interacted with.\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.\n- `destroy(): Promise<void>` - Permanently destroy the component.\n- `nextMedia(contentElementIndex: number): Promise<void>` - Paginates to the next [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info.\n- `previousMedia(contentElementIndex: number): Promise<void>` - Paginates to the previous [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info in the specified\n[media](esri-popup-content-MediaContent.html) content element.\n- `setActiveMedia(contentElementIndex: number, mediaInfoIndex: number): Promise<void>` - Paginates to a specified [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info object. For example,\nyou may have [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) content which contains\nmultiple `mediaInfos`. This method allows you to specify the index of the `mediaInfos`\nyou wish to display.\n\n::: esri-md class=\"warning\"\nPrior to   version 4.17, this method was named `goToMedia`.\n:::\n- `updateGeometry(): Promise<void>` - Updates the geometry of the graphic.",
           "doc-url": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/",
           "attributes": [
             {
@@ -5406,7 +5420,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.",
               "default": "2",
               "value": {
                 "type": [
@@ -5435,6 +5449,46 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "hide-content-attachments",
+              "description": "**Deprecated**: since 4.34, use [`hideAttachmentsContent`](#hideAttachmentsContent) instead.. Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "hide-content-expression",
+              "description": "**Deprecated**: since 4.34, use [`hideExpressionContent`](#hideExpressionContent) instead.. Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "hide-content-fields",
+              "description": "**Deprecated**: since 4.34, use [`hideFieldsContent`](#hideFieldsContent) instead.. Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "hide-content-media",
+              "description": "**Deprecated**: since 4.34, use [`hideMediaContent`](#hideMediaContent) instead.. Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "hide-content-text",
+              "description": "**Deprecated**: since 4.34, use [`hideTextContent`](#hideTextContent) instead.. Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
             {
               "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.",
@@ -5467,6 +5521,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "hide-last-edit-info",
+              "description": "**Deprecated**: since 4.33, use [`hideLastEditedInfo`](#hideLastEditedInfo) instead.. Indicates whether to hide the title associated with the feature.",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
             {
               "name": "hide-last-edited-info",
               "description": "This property provides the ability to hide or show the last edited info within the component.",
@@ -5491,6 +5553,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "hide-title",
+              "description": "**Deprecated**: since 4.34, use [`hideHeading`](#hideHeading) instead.. Indicates whether to hide the title associated with the feature.",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
             {
               "name": "icon",
               "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
@@ -5548,7 +5618,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -5561,7 +5631,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).",
               "value": {
                 "type": "string"
               }
@@ -5598,7 +5668,8 @@
               },
               {
                 "name": "flowItems",
-                "type": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>"
+                "description": "A collection of flow items that are used to manage drill-in navigation.",
+                "type": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>"
               },
               {
                 "name": "graphic",
@@ -5612,7 +5683,7 @@
               },
               {
                 "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": "1 | 2 | 3 | 4 | 5 | 6"
               },
               {
@@ -5625,6 +5696,31 @@
                 "description": "This property provides the ability to hide or show content within the component.",
                 "type": "boolean"
               },
+              {
+                "name": "hideContentAttachments",
+                "description": "Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+                "type": "boolean"
+              },
+              {
+                "name": "hideContentExpression",
+                "description": "Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
+                "type": "boolean"
+              },
+              {
+                "name": "hideContentFields",
+                "description": "Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
+                "type": "boolean"
+              },
+              {
+                "name": "hideContentMedia",
+                "description": "Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+                "type": "boolean"
+              },
+              {
+                "name": "hideContentText",
+                "description": "Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+                "type": "boolean"
+              },
               {
                 "name": "hideCustomContent",
                 "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.",
@@ -5650,6 +5746,11 @@
                 "description": "This property provides the ability to hide or show the last edited info within the component.",
                 "type": "boolean"
               },
+              {
+                "name": "hideLastEditInfo",
+                "description": "Indicates whether to hide the title associated with the feature.",
+                "type": "boolean"
+              },
               {
                 "name": "hideMediaContent",
                 "description": "This property provides the ability to hide or show [media content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) within the component.",
@@ -5660,6 +5761,11 @@
                 "description": "This property provides the ability to hide or show [text content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html) within the component.",
                 "type": "boolean"
               },
+              {
+                "name": "hideTitle",
+                "description": "Indicates whether to hide the title associated with the feature.",
+                "type": "boolean"
+              },
               {
                 "name": "icon",
                 "description": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
@@ -5667,7 +5773,7 @@
               },
               {
                 "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": "boolean"
               },
               {
@@ -5716,17 +5822,17 @@
               },
               {
                 "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": "\"disabled\" | \"error\" | \"loading\" | \"ready\""
               },
               {
                 "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": "string"
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -5795,7 +5901,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).",
               "default": "\"form-field\"",
               "value": {
                 "type": "string"
@@ -5834,7 +5940,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -5907,7 +6013,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": "string"
               },
               {
@@ -5931,7 +6037,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": "\"disabled\" | \"ready\""
               },
               {
@@ -6193,7 +6299,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).",
               "default": "\"table\"",
               "value": {
                 "type": "string"
@@ -6368,7 +6474,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -6427,7 +6533,7 @@
             },
             {
               "name": "arcgisPropertyChange",
-              "type": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+              "type": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
               "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties."
             },
             {
@@ -6669,7 +6775,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": "string"
               },
               {
@@ -6838,7 +6944,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": "\"disabled\" | \"error\" | \"loaded\" | \"loading\" | \"ready\""
               },
               {
@@ -6903,7 +7009,7 @@
               },
               {
                 "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": "LinkChartView | MapView | SceneView"
               },
               {
@@ -6935,7 +7041,7 @@
               },
               {
                 "name": "arcgisPropertyChange",
-                "type": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+                "type": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
                 "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties."
               },
               {
@@ -7003,7 +7109,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).",
               "default": "\"list-rectangle\"",
               "value": {
                 "type": "string"
@@ -7052,7 +7158,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -7117,7 +7223,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": "string"
               },
               {
@@ -7146,7 +7252,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": "\"disabled\" | \"loading\" | \"ready\""
               }
             ],
@@ -7181,6 +7287,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "closed",
+              "description": "**Deprecated**: since 4.34, use [`visible`](#visible) instead.. Indicates whether a component is closed. When `true`, the component will be hidden.",
+              "default": "false",
+              "value": {
+                "type": "boolean"
+              }
+            },
             {
               "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`.",
@@ -7235,6 +7349,13 @@
                 "type": "number"
               }
             },
+            {
+              "name": "features-title",
+              "description": "**Deprecated**: since 4.34, use [`heading`](#heading) instead.. The title of the Features component.",
+              "value": {
+                "type": "string"
+              }
+            },
             {
               "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.",
@@ -7323,8 +7444,8 @@
             },
             {
               "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)",
-              "default": "true",
+              "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.",
+              "default": "false",
               "value": {
                 "type": "boolean"
               }
@@ -7403,7 +7524,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -7436,7 +7557,7 @@
             },
             {
               "name": "arcgisPropertyChange",
-              "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+              "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
               "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties."
             },
             {
@@ -7467,6 +7588,11 @@
                 "description": "If true, the component will not be destroyed automatically when it is\ndisconnected from the document. This is useful when you want to move the\ncomponent to a different place on the page, or temporarily hide it. If this\nis set, make sure to call the [destroy](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-features/#destroy) method when you are done to\nprevent memory leaks.",
                 "type": "boolean"
               },
+              {
+                "name": "closed",
+                "description": "Indicates whether a component is closed. When `true`, the component will be hidden.",
+                "type": "boolean"
+              },
               {
                 "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`.",
@@ -7512,6 +7638,11 @@
                 "description": "The number of features to fetch at one time.",
                 "type": "number"
               },
+              {
+                "name": "featuresTitle",
+                "description": "The title of the Features component.",
+                "type": "string"
+              },
               {
                 "name": "featureViewModelAbilities",
                 "description": "Defines the specific [abilities](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#Abilities) that can be used when querying and displaying content.",
@@ -7579,7 +7710,7 @@
               },
               {
                 "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": "boolean"
               },
               {
@@ -7658,7 +7789,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": "\"disabled\" | \"ready\""
               },
               {
@@ -7668,7 +7799,7 @@
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -7689,7 +7820,7 @@
               },
               {
                 "name": "arcgisPropertyChange",
-                "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+                "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
                 "description": "Emitted when the value of a property is changed. Use this to listen to changes to properties."
               },
               {
@@ -7735,7 +7866,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).",
               "default": "\"urban-model\"",
               "value": {
                 "type": "string"
@@ -7821,7 +7952,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": "string"
               },
               {
@@ -7855,7 +7986,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -8407,7 +8538,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -8455,7 +8586,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).",
               "default": "\"arrow-double-horizontal\"",
               "value": {
                 "type": "string"
@@ -8555,7 +8686,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.",
               "value": {
                 "type": [
                   "\"disabled\"",
@@ -8615,7 +8746,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": "string"
               },
               {
@@ -8674,7 +8805,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": "\"disabled\" | \"ready\""
               },
               {
@@ -8751,7 +8882,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -8817,12 +8948,12 @@
               },
               {
                 "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": "\"disabled\" | \"going-home\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -8934,7 +9065,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).",
               "default": "\"layers\"",
               "value": {
                 "type": "string"
@@ -9044,7 +9175,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -9154,7 +9285,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": "string"
               },
               {
@@ -9237,7 +9368,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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
@@ -9247,7 +9378,7 @@
               },
               {
                 "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": "MapView | SceneView"
               },
               {
@@ -9420,7 +9551,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -9530,12 +9661,12 @@
               },
               {
                 "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": "\"disabled\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -9673,6 +9804,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -10340,7 +10472,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.",
               "default": "\"loading\"",
               "value": {
                 "type": [
@@ -10421,12 +10553,12 @@
               },
               {
                 "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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
                 "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": "LinkChartView"
               }
             ],
@@ -10472,6 +10604,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).",
               "default": "\"gps-off\"",
               "value": {
                 "type": "string"
@@ -10584,6 +10717,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": "string"
               },
               {
@@ -10621,7 +10755,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -11312,7 +11446,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).",
               "default": "\"measure\"",
               "value": {
                 "type": "string"
@@ -11372,7 +11506,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -11420,7 +11554,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": "string"
               },
               {
@@ -11444,12 +11578,12 @@
               },
               {
                 "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": "\"disabled\" | \"measured\" | \"measuring\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -11598,6 +11732,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -11662,7 +11797,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).",
               "default": "\"oriented-imagery-widget\"",
               "value": {
                 "type": "string"
@@ -11795,7 +11930,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": "string"
               },
               {
@@ -11863,7 +11998,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -11931,6 +12066,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "LinkChartView | MapView | SceneView"
               }
             ],
@@ -12142,7 +12278,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -12168,7 +12304,7 @@
             },
             {
               "name": "arcgisPropertyChange",
-              "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }"
+              "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }"
             },
             {
               "name": "arcgisReady",
@@ -12363,7 +12499,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": "\"disabled\" | \"ready\""
               },
               {
@@ -12380,7 +12516,7 @@
               },
               {
                 "name": "arcgisPropertyChange",
-                "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }"
+                "type": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }"
               },
               {
                 "name": "arcgisReady",
@@ -12687,7 +12823,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -12840,7 +12976,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -12897,7 +13033,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).",
               "default": "\"actual-size\"",
               "value": {
                 "type": "string"
@@ -12976,7 +13112,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -13024,7 +13160,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": "string"
               },
               {
@@ -13078,12 +13214,12 @@
               },
               {
                 "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": "\"disabled\" | \"ready\""
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -13943,7 +14079,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.",
               "default": "\"ready\"",
               "value": {
                 "type": [
@@ -14163,7 +14299,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": "\"disabled\" | \"loading\" | \"ready\" | \"searching\""
               },
               {
@@ -14178,7 +14314,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -14383,7 +14519,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).",
               "default": "\"measure-building-height-shadow\"",
               "value": {
                 "type": "string"
@@ -14545,7 +14681,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": "string"
               },
               {
@@ -14584,7 +14720,7 @@
               },
               {
                 "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": "SceneView"
               },
               {
@@ -14799,7 +14935,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).",
               "default": "\"pencil\"",
               "value": {
                 "type": "string"
@@ -14868,7 +15004,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.",
               "value": {
                 "type": [
                   "\"active\"",
@@ -15041,7 +15177,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": "string"
               },
               {
@@ -15057,7 +15193,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": "GraphicsLayer"
+                "type": "GraphicsLayer | MapNotesLayer"
               },
               {
                 "name": "layout",
@@ -15104,7 +15240,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": "\"active\" | \"disabled\" | \"ready\""
               },
               {
@@ -15124,7 +15260,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -15339,6 +15475,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -15446,7 +15583,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -15544,7 +15681,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": "\"disabled\" | \"ready\""
               },
               {
@@ -15559,7 +15696,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -15656,7 +15793,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).",
               "default": "\"table\"",
               "value": {
                 "type": "string"
@@ -15766,7 +15903,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -15846,7 +15983,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": "string"
               },
               {
@@ -15859,6 +15996,11 @@
                 "description": "Specifies a function that accesses each [ListItem](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList-ListItem.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList.html#listItemCreatedFunction)",
                 "type": "(((event: TableListListItemCreatedHandlerEvent) => void))"
               },
+              {
+                "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": "Map | WebMap"
+              },
               {
                 "name": "minDragEnabledItems",
                 "description": "The minimum number of list items required to enable drag and drop reordering with [dragEnabled](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList.html#dragEnabled).",
@@ -15914,13 +16056,18 @@
               },
               {
                 "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": "\"disabled\" | \"loading\" | \"ready\""
               },
               {
                 "name": "tableItems",
                 "description": "The collection of table ListItems displayed within the component.",
                 "type": "Collection<TableListListItem>"
+              },
+              {
+                "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": "LinkChartView | MapView | SceneView"
               }
             ],
             "events": [
@@ -15970,7 +16117,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).",
               "default": "\"clock\"",
               "value": {
                 "type": "string"
@@ -16050,7 +16197,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.",
               "default": "\"disabled\"",
               "value": {
                 "type": [
@@ -16122,7 +16269,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": "string"
               },
               {
@@ -16161,7 +16308,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": "\"disabled\" | \"playing\" | \"ready\""
               },
               {
@@ -16191,7 +16338,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -16393,6 +16540,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).",
               "default": "\"compass-north-circle\"",
               "value": {
                 "type": "string"
@@ -16515,6 +16663,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": "string"
               },
               {
@@ -16563,7 +16712,7 @@
               },
               {
                 "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": "MapView | SceneView"
               }
             ],
@@ -16654,7 +16803,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).",
               "default": "\"view-associations\"",
               "value": {
                 "type": "string"
@@ -16934,7 +17083,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": "string"
               },
               {
@@ -17028,7 +17177,7 @@
               },
               {
                 "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": "MapView"
               },
               {
@@ -17114,17 +17263,9 @@
                 "type": "boolean"
               }
             },
-            {
-              "name": "gdb-version",
-              "description": "**Deprecated**: `gdbVersion` is deprecated since version 4.31.. The Geodatabase version to pass into the trace.",
-              "default": "\"sde.DEFAULT\"",
-              "value": {
-                "type": "string"
-              }
-            },
             {
               "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).",
               "default": "\"utility-network-trace\"",
               "value": {
                 "type": "string"
@@ -17187,7 +17328,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.",
               "default": "\"ready\"",
               "value": {
                 "type": [
@@ -17256,14 +17397,9 @@
                 "description": "An array of map points to load into the widget to lookup flags.",
                 "type": "Array<FlagProperty>"
               },
-              {
-                "name": "gdbVersion",
-                "description": "The Geodatabase version to pass into the trace.",
-                "type": "string"
-              },
               {
                 "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": "string"
               },
               {
@@ -17312,7 +17448,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": "\"loading\" | \"ready\""
               },
               {
@@ -17322,7 +17458,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -17414,7 +17550,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.",
               "value": {
                 "type": [
                   "\"disabled\"",
@@ -17475,8 +17611,13 @@
               },
               {
                 "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": "\"disabled\" | \"executing\" | \"loading\" | \"ready\""
+              },
+              {
+                "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": "MapView"
               }
             ],
             "events": [
@@ -17534,6 +17675,61 @@
             ]
           }
         },
+        {
+          "name": "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.\n--\n\n### Events\n- **arcgisTraceInputsChange**\n- **arcgisUtilityNetworkChange**\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.",
+          "doc-url": "https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-utility-network-trace-inputs/",
+          "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.",
+              "value": {
+                "type": "string"
+              }
+            }
+          ],
+          "events": [
+            {
+              "name": "arcgisTraceInputsChange",
+              "type": "void"
+            },
+            {
+              "name": "arcgisUtilityNetworkChange",
+              "type": "void"
+            }
+          ],
+          "js": {
+            "properties": [
+              {
+                "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": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string"
+              },
+              {
+                "name": "selectedTraceConfiguration",
+                "type": "NamedTraceConfiguration"
+              },
+              {
+                "name": "selectedUtilityNetwork",
+                "type": "UtilityNetwork"
+              },
+              {
+                "name": "view",
+                "type": "MapView | undefined"
+              }
+            ],
+            "events": [
+              {
+                "name": "arcgisTraceInputsChange",
+                "type": "void"
+              },
+              {
+                "name": "arcgisUtilityNetworkChange",
+                "type": "void"
+              }
+            ]
+          }
+        },
         {
           "name": "arcgis-utility-network-validate-topology",
           "description": "The UtilityNetworkValidateTopology component simplifies the process of validating a DirtyArea within a utility network. It offers an intuitive user interface, reducing the complexity of working with utility network associations.\n\n> The UtilityNetworkValidateTopology Component does not support proxied feature services or feature services that utilize stored credentials.\n--\n\n### Events\n- **arcgisPropertyChange** - Emitted when the value of a property is changed. Use this to listen to changes to properties.\n- **arcgisReady** - Emitted when the component associated with a map or scene view is ready to be interacted with.\n\n### Methods\n- `componentOnReady(): Promise<void>` - Create a promise that resolves once component is fully loaded.\n- `destroy(): Promise<void>` - Permanently destroy the component.",
@@ -17560,7 +17756,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).",
               "default": "\"check-circle\"",
               "value": {
                 "type": "string"
@@ -17599,7 +17795,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.",
               "default": "\"ready\"",
               "value": {
                 "type": [
@@ -17639,7 +17835,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": "string"
               },
               {
@@ -17658,7 +17854,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": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\""
               },
               {
@@ -17668,7 +17864,7 @@
               },
               {
                 "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": "MapView"
               }
             ],
@@ -17754,7 +17950,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).",
               "default": "\"list-rectangle\"",
               "value": {
                 "type": "string"
@@ -17897,7 +18093,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": "string"
               },
               {
@@ -17998,6 +18194,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).",
               "value": {
                 "type": "string"
               }
@@ -18048,7 +18245,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.",
               "value": {
                 "type": [
                   "\"disabled\"",
@@ -18089,6 +18286,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": "string"
               },
               {
@@ -18125,7 +18323,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": "\"disabled\" | \"executing\" | \"failed\" | \"loading\" | \"ready\" | \"success\""
               },
               {
@@ -18314,7 +18512,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.",
               "value": {
                 "type": [
                   "\"can-play\"",
@@ -18393,7 +18591,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": "\"can-play\" | \"data-loaded\" | \"error\" | \"not-ready\" | \"paused\" | \"playing\" | \"ready\" | \"waiting\""
               }
             ],
@@ -18563,6 +18761,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "SceneView"
               }
             ],
@@ -18710,6 +18909,7 @@
               },
               {
                 "name": "view",
+                "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
                 "type": "MapView | SceneView"
               }
             ],