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

package/dist/docs/docs.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-09-15T04:38:05",
+  "timestamp": "2025-09-17T19:21:48",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "4.34.0-next.132",
+    "version": "4.34.0-next.134",
     "typescriptVersion": "5.8.3"
   },
   "components": [
@@ -61,7 +61,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -237,7 +237,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D-AreaMeasurement2DViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -386,7 +386,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -910,7 +910,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -1392,7 +1392,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -1546,7 +1546,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Attachments-AttachmentsViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -2045,7 +2045,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -2095,7 +2095,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -2661,7 +2661,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -3118,7 +3118,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList-BasemapLayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -3164,7 +3164,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -3640,7 +3640,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -3690,7 +3690,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -4565,7 +4565,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -4634,7 +4634,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -4973,8 +4973,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "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/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"organization\"",
           "values": [
             {
@@ -5248,7 +5253,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -5633,7 +5638,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -6020,7 +6025,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList-CatalogLayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -6066,7 +6071,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -6512,7 +6517,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -6558,7 +6563,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -6954,7 +6959,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -7238,7 +7243,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-CoordinateConversionViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -7333,7 +7338,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -7622,7 +7627,7 @@
           "required": false
         },
         {
-          "name": "directShadowsEnabled",
+          "name": "directShadowsDisabled",
           "type": "boolean",
           "complexType": {
             "original": "boolean",
@@ -7630,7 +7635,7 @@
             "references": {}
           },
           "mutable": true,
-          "attr": "direct-shadows-enabled",
+          "attr": "direct-shadows-disabled",
           "reflectToAttr": false,
           "docs": "",
           "docsTags": [],
@@ -7902,10 +7907,10 @@
         },
         {
           "name": "localDate",
-          "type": "Date",
+          "type": "Date | number | string",
           "complexType": {
-            "original": "Date",
-            "resolved": "Date",
+            "original": "Date | number | string",
+            "resolved": "Date | number | string",
             "references": {
               "Date": {
                 "location": "import",
@@ -7915,10 +7920,21 @@
             }
           },
           "mutable": true,
+          "attr": "local-date",
           "reflectToAttr": false,
           "docs": "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).",
           "docsTags": [],
-          "values": [],
+          "values": [
+            {
+              "type": "Date"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "string"
+            }
+          ],
           "optional": true,
           "required": false
         },
@@ -8677,7 +8693,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -8717,7 +8733,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -9032,7 +9048,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -9302,7 +9318,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "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)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -9452,7 +9468,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -10018,10 +10034,10 @@
         },
         {
           "name": "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -10054,7 +10070,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -10567,10 +10583,10 @@
         },
         {
           "name": "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -10608,7 +10624,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [
             {
               "name": "inheritedFrom",
@@ -10838,7 +10854,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -11014,7 +11030,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D-DistanceMeasurement2DViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -11115,10 +11131,10 @@
         },
         {
           "name": "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -11151,7 +11167,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -11596,7 +11612,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -11843,7 +11859,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor-EditorViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -11984,7 +12000,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -12648,8 +12664,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "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/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"altitude\"",
           "values": [
             {
@@ -12760,27 +12781,27 @@
         },
         {
           "name": "profiles",
-          "type": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
+          "type": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
           "complexType": {
-            "original": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
-            "resolved": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
+            "original": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
+            "resolved": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineGround": {
+              "ElevationProfileElevationProfileLineGround": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineInput": {
+              "ElevationProfileElevationProfileLineInput": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineQuery": {
+              "ElevationProfileElevationProfileLineQuery": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
@@ -13018,10 +13039,10 @@
         },
         {
           "name": "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -13059,7 +13080,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -13674,32 +13695,32 @@
         },
         {
           "name": "profiles",
-          "type": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
+          "type": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
           "complexType": {
-            "original": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
-            "resolved": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
+            "original": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
+            "resolved": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileGroundLine": {
+              "ElevationProfileLineGround": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileInputLine": {
+              "ElevationProfileLineInput": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileQueryLine": {
+              "ElevationProfileLineQuery": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileSceneLine": {
+              "ElevationProfileLineScene": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
@@ -13996,10 +14017,10 @@
         },
         {
           "name": "unitOptionsDistance",
-          "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -14018,10 +14039,10 @@
         },
         {
           "name": "unitOptionsElevation",
-          "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\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -14059,7 +14080,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -14309,7 +14330,7 @@
           "required": false
         },
         {
-          "name": "closeOnEsc",
+          "name": "closeOnEscDisabled",
           "type": "(((event: KeyboardEvent) => boolean)) | boolean",
           "complexType": {
             "original": "(((event: KeyboardEvent) => boolean)) | boolean",
@@ -14323,9 +14344,9 @@
             }
           },
           "mutable": true,
-          "attr": "close-on-esc",
+          "attr": "close-on-esc-disabled",
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [
             {
               "name": "example",
@@ -14333,10 +14354,10 @@
             },
             {
               "name": "example",
-              "text": "```html\n<arcgis-expand slot=\"top-right\">\n  <arcgis-search></arcgis-search>\n</arcgis-expand>\n\n<script>\n const expandElement = document.querySelector(\"arcgis-expand\");\n const searchElement = document.querySelector(\"arcgis-search\");\n expandElement.closeOnEsc = () => {\n    // only close the expand if the search is not active\n    return searchElement.activeMenu === \"none\";\n };\n</script>\n```"
+              "text": "```html\n<arcgis-expand slot=\"top-right\">\n  <arcgis-search></arcgis-search>\n</arcgis-expand>\n\n<script>\n const expandElement = document.querySelector(\"arcgis-expand\");\n const searchElement = document.querySelector(\"arcgis-search\");\n // don't close the expand if the search is active\n expandElement.closeOnEscDisabled = () => searchElement.activeMenu !== \"none\";\n</script>\n```"
             }
           ],
-          "default": "true",
+          "default": "false",
           "values": [
             {
               "type": "(((event: KeyboardEvent) => boolean))"
@@ -14848,7 +14869,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -14890,7 +14911,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -15106,7 +15127,12 @@
           "attr": "chart-animation-disabled",
           "reflectToAttr": false,
           "docs": "Disables chart animation within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15140,22 +15166,22 @@
         },
         {
           "name": "flowItems",
-          "type": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
+          "type": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
           "complexType": {
-            "original": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
-            "resolved": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
+            "original": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
+            "resolved": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "HTMLArcgisFeatureRelationshipElement": {
+              "HTMLArcgisFeatureElement": {
                 "location": "local",
                 "path": "index.js",
                 "id": "notImplemented"
               },
-              "HTMLArcgisFeatureElement": {
+              "HTMLArcgisFeatureRelationshipElement": {
                 "location": "local",
                 "path": "index.js",
                 "id": "notImplemented"
@@ -15164,8 +15190,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "A collection of flow items that are used to manage drill-in navigation.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -15217,6 +15248,10 @@
           "reflectToAttr": false,
           "docs": "The title for the feature. This can be disabled by setting the [`hideHeading`](#hideHeading) property to `true`.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "see",
               "text": "[headingLevel](#headingLevel)"
@@ -15250,7 +15285,7 @@
           "mutable": true,
           "attr": "heading-level",
           "reflectToAttr": false,
-          "docs": "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.",
+          "docs": "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.",
           "docsTags": [
             {
               "name": "see",
@@ -15325,8 +15360,128 @@
           "attr": "hide-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show content within the component.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentAttachments",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-attachments",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideAttachmentsContent`](#hideAttachmentsContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentExpression",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-expression",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
           "docsTags": [],
           "default": "false",
+          "deprecation": "since 4.34, use [`hideExpressionContent`](#hideExpressionContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentFields",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-fields",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideFieldsContent`](#hideFieldsContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentMedia",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-media",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideMediaContent`](#hideMediaContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentText",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-text",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideTextContent`](#hideTextContent) instead.",
           "values": [
             {
               "type": "boolean"
@@ -15347,7 +15502,12 @@
           "attr": "hide-custom-content",
           "reflectToAttr": false,
           "docs": "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.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15413,7 +15573,12 @@
           "attr": "hide-heading",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show the component's [heading](#heading).",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15445,6 +15610,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "hideLastEditInfo",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-last-edit-info",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide the title associated with the feature.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.33, use [`hideLastEditedInfo`](#hideLastEditedInfo) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "hideMediaContent",
           "type": "boolean",
@@ -15489,6 +15677,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "hideTitle",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-title",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide the title associated with the feature.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideHeading`](#hideHeading) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "icon",
           "type": "string",
@@ -15526,8 +15737,12 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "Indicates whether the current graphic resides in a non-spatial table.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -15636,7 +15851,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "Overwrite localized strings for this component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -15759,7 +15979,12 @@
           "attr": "show-relationship-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [relationship content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15781,7 +16006,12 @@
           "attr": "show-utility-network-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [utility network content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15837,7 +16067,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -15877,7 +16107,7 @@
           "mutable": true,
           "attr": "time-zone",
           "reflectToAttr": false,
-          "docs": "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).",
+          "docs": "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).",
           "docsTags": [],
           "values": [
             {
@@ -15908,7 +16138,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -16135,8 +16365,13 @@
           },
           "signature": "updateGeometry(): Promise<void>",
           "parameters": [],
-          "docs": "",
-          "docsTags": []
+          "docs": "Updates the geometry of the graphic.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         }
       ],
       "events": [
@@ -16353,7 +16588,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -16573,7 +16808,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FeatureFormViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -17997,7 +18232,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "The string value which indicates the displayed [icon](https://developers.arcgis.com/calcite-design-system/icons/).",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -18965,7 +19200,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -19307,7 +19542,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -20050,11 +20285,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+          "detail": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
-            "resolved": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+            "original": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
+            "resolved": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -20284,7 +20519,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -20516,7 +20751,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -20773,6 +21008,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "closed",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "closed",
+          "reflectToAttr": false,
+          "docs": "Indicates whether a component is closed. When `true`, the component will be hidden.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`visible`](#visible) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "collapsed",
           "type": "boolean",
@@ -20875,6 +21133,10 @@
           "reflectToAttr": false,
           "docs": "The number of selected [features](#features) available to the popup.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -20901,7 +21163,12 @@
           "attr": "feature-menu-open",
           "reflectToAttr": false,
           "docs": "This property enables multiple features in the component to display in a list rather than displaying the first selected feature.\nSetting this to `true` allows the user to scroll through the list of features.\nThis value will only be honored if [`initialDisplayMode`](#initialDisplayMode) is set to \"feature\".",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -20944,7 +21211,12 @@
           "attr": "feature-navigation-top",
           "reflectToAttr": false,
           "docs": "Indicates whether the feature navigation arrows are displayed at the top of the component.\nBy default, the navigation arrows are displayed at the bottom of the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -21011,6 +21283,28 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "featuresTitle",
+          "type": "string",
+          "complexType": {
+            "original": "string",
+            "resolved": "string",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "features-title",
+          "reflectToAttr": false,
+          "docs": "The title of the Features component.",
+          "docsTags": [],
+          "deprecation": "since 4.34, use [`heading`](#heading) instead.",
+          "values": [
+            {
+              "type": "string"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "featureViewModelAbilities",
           "type": "Abilities",
@@ -21351,9 +21645,14 @@
           "mutable": true,
           "attr": "highlight-disabled",
           "reflectToAttr": false,
-          "docs": "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)",
-          "docsTags": [],
-          "default": "true",
+          "docs": "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.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
+          "default": "false",
           "values": [
             {
               "type": "boolean"
@@ -21669,6 +21968,10 @@
           "reflectToAttr": false,
           "docs": "The feature that the component has drilled into.\nThis feature is either associated with the selected feature in a [relationship](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) or [utility network](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkAssociationsContent.html) element.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -21723,6 +22026,10 @@
           "reflectToAttr": false,
           "docs": "Returns a reference to the current [arcgis-feature](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/) component.\nThis is useful if needing to get a reference to the Feature component in order to make any changes to it.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -21821,7 +22128,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -21884,8 +22191,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
-          "docsTags": [],
+          "docs": "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.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [
             {
               "type": "MapView"
@@ -21942,6 +22254,10 @@
             {
               "name": "type",
               "text": "{boolean}"
+            },
+            {
+              "name": "since",
+              "text": "4.34"
             }
           ],
           "default": "false",
@@ -22326,11 +22642,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
-            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
+            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -22493,7 +22809,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -22721,7 +23037,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -24073,7 +24389,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -24401,7 +24717,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -24762,7 +25078,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Slider-SliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -25177,7 +25493,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -25223,7 +25539,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -25753,7 +26069,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -26250,7 +26566,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList-LayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -26323,7 +26639,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -27183,7 +27499,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -27225,7 +27541,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -27622,7 +27938,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -30242,7 +30558,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -30283,7 +30599,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -30579,8 +30895,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"gps-off\"",
           "values": [
             {
@@ -30836,7 +31157,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the Module.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -33670,7 +33991,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -33894,7 +34215,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement-MeasurementViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -33944,7 +34265,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -34388,7 +34709,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -34630,7 +34951,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -35022,7 +35343,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -35283,7 +35604,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -36555,7 +36876,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -36993,11 +37314,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
+          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
-            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
+            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
+            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -37747,7 +38068,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -38173,7 +38494,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -38401,7 +38722,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -38727,7 +39048,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider-ScaleRangeSliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -38769,7 +39090,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -42383,7 +42704,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -42488,7 +42809,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -43408,8 +43729,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "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/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"measure-building-height-shadow\"",
           "values": [
             {
@@ -43659,7 +43985,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -44582,7 +44908,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -44643,15 +44969,20 @@
         },
         {
           "name": "layer",
-          "type": "GraphicsLayer",
+          "type": "GraphicsLayer | MapNotesLayer",
           "complexType": {
-            "original": "GraphicsLayer",
-            "resolved": "GraphicsLayer",
+            "original": "GraphicsLayer | MapNotesLayer",
+            "resolved": "GraphicsLayer | MapNotesLayer",
             "references": {
               "GraphicsLayer": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
+              },
+              "MapNotesLayer": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
               }
             }
           },
@@ -44659,7 +44990,14 @@
           "reflectToAttr": false,
           "docs": "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)",
           "docsTags": [],
-          "values": [],
+          "values": [
+            {
+              "type": "GraphicsLayer"
+            },
+            {
+              "type": "MapNotesLayer"
+            }
+          ],
           "optional": true,
           "required": false
         },
@@ -45032,7 +45370,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The Sketch widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -45158,7 +45496,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -46057,7 +46395,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -46548,7 +46886,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the Swipe.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -46634,7 +46972,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -47008,7 +47346,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -47061,6 +47399,40 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "map",
+          "type": "Map | WebMap",
+          "complexType": {
+            "original": "Map | WebMap",
+            "resolved": "Map | WebMap",
+            "references": {
+              "Map": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "WebMap": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "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)",
+          "docsTags": [],
+          "values": [
+            {
+              "type": "Map"
+            },
+            {
+              "type": "WebMap"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "minDragEnabledItems",
           "type": "number",
@@ -47416,7 +47788,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList-TableListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -47472,6 +47844,48 @@
           "values": [],
           "optional": true,
           "required": false
+        },
+        {
+          "name": "view",
+          "type": "LinkChartView | MapView | SceneView",
+          "complexType": {
+            "original": "LinkChartView | MapView | SceneView",
+            "resolved": "LinkChartView | MapView | SceneView",
+            "references": {
+              "LinkChartView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "SceneView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+          "docsTags": [],
+          "values": [
+            {
+              "type": "LinkChartView"
+            },
+            {
+              "type": "MapView"
+            },
+            {
+              "type": "SceneView"
+            }
+          ],
+          "optional": true,
+          "required": false
         }
       ],
       "methods": [
@@ -47764,7 +48178,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -48028,7 +48442,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider-TimeSliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -48211,7 +48625,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -49003,8 +49417,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"compass-north-circle\"",
           "values": [
             {
@@ -49330,7 +49749,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Track-TrackViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -49753,7 +50172,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -50261,7 +50680,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -50738,29 +51157,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "gdbVersion",
-          "type": "string",
-          "complexType": {
-            "original": "string",
-            "resolved": "string",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "gdb-version",
-          "reflectToAttr": false,
-          "docs": "The Geodatabase version to pass into the trace.",
-          "docsTags": [],
-          "default": "\"sde.DEFAULT\"",
-          "deprecation": "`gdbVersion` is deprecated since version 4.31.",
-          "values": [
-            {
-              "type": "string"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
         {
           "name": "icon",
           "type": "string",
@@ -50772,7 +51168,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -51066,7 +51462,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace-UtilityNetworkTraceViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -51135,7 +51531,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -51605,7 +52001,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -51632,6 +52028,485 @@
           ],
           "optional": true,
           "required": false
+        },
+        {
+          "name": "view",
+          "type": "MapView",
+          "complexType": {
+            "original": "MapView",
+            "resolved": "MapView",
+            "references": {
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "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)",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        }
+      ],
+      "methods": [
+        {
+          "name": "componentOnReady",
+          "returns": {
+            "type": "Promise<void>",
+            "docs": ""
+          },
+          "complexType": {
+            "signature": "(): Promise<void>",
+            "parameters": [],
+            "return": "Promise<void>",
+            "references": {
+              "Promise": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "signature": "componentOnReady(): Promise<void>",
+          "parameters": [],
+          "docs": "Create a promise that resolves once component is fully loaded.",
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\nconst arcgisUtilityNetworkTraceAnalysis = document.querySelector(\"arcgis-utility-network-trace-analysis\");\ndocument.body.append(arcgisUtilityNetworkTraceAnalysis);\nawait arcgisUtilityNetworkTraceAnalysis.componentOnReady();\nconsole.log(\"arcgis-utility-network-trace-analysis is ready to go!\");\n```"
+            },
+            {
+              "name": "inheritedFrom",
+              "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+            }
+          ]
+        },
+        {
+          "name": "destroy",
+          "returns": {
+            "type": "Promise<void>",
+            "docs": ""
+          },
+          "complexType": {
+            "signature": "(): Promise<void>",
+            "parameters": [],
+            "return": "Promise<void>",
+            "references": {
+              "Promise": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "signature": "destroy(): Promise<void>",
+          "parameters": [],
+          "docs": "Permanently destroy the component.",
+          "docsTags": []
+        }
+      ],
+      "events": [
+        {
+          "event": "arcgisPropertyChange",
+          "detail": "never",
+          "bubbles": true,
+          "complexType": {
+            "original": "never",
+            "resolved": "never",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "",
+          "docsTags": []
+        },
+        {
+          "event": "arcgisReady",
+          "detail": "void",
+          "bubbles": true,
+          "complexType": {
+            "original": "void",
+            "resolved": "void",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "Emitted when the component associated with a map or scene view is ready to be interacted with.",
+          "docsTags": []
+        }
+      ],
+      "styles": [],
+      "slots": [],
+      "parts": [],
+      "listeners": []
+    },
+    {
+      "filePath": "src/components/utility-network-trace-analysis/components/result-feature-list/result-feature-list.tsx",
+      "tag": "arcgis-result-feature-list",
+      "overview": "",
+      "readme": "",
+      "usage": {},
+      "docs": "This is a sub-component used by the **ArcgisUtilityNetworkTraceAnalysis** component.\n\nThis sub-component takes trace result elements as input.\nIt displays the layers the elements are from, with a count of elements on each layer.\nA `UtilityNetwork` and list of layers is required to display feature layer names.",
+      "docsTags": [
+        {
+          "name": "since",
+          "text": "4.34"
+        },
+        {
+          "name": "superclass",
+          "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+        }
+      ],
+      "encapsulation": "shadow",
+      "dependents": [],
+      "dependencies": [],
+      "dependencyGraph": {},
+      "props": [
+        {
+          "name": "elements",
+          "type": "Array<NetworkElement>",
+          "complexType": {
+            "original": "Array<NetworkElement>",
+            "resolved": "Array<NetworkElement>",
+            "references": {
+              "Array": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              },
+              "NetworkElement": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [
+            {
+              "name": "required"
+            }
+          ],
+          "values": [],
+          "optional": false,
+          "required": true
+        },
+        {
+          "name": "layers",
+          "type": "Array<Layer>",
+          "complexType": {
+            "original": "Array<Layer>",
+            "resolved": "Array<Layer>",
+            "references": {
+              "Array": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              },
+              "Layer": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [
+            {
+              "name": "required"
+            }
+          ],
+          "values": [],
+          "optional": false,
+          "required": true
+        },
+        {
+          "name": "messageOverrides",
+          "type": "Record<string, unknown>",
+          "complexType": {
+            "original": "Record<string, unknown>",
+            "resolved": "Record<string, unknown>",
+            "references": {}
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "selectedLayer",
+          "type": "Layer",
+          "complexType": {
+            "original": "Layer",
+            "resolved": "Layer",
+            "references": {
+              "Layer": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "utilityNetwork",
+          "type": "UtilityNetwork | undefined",
+          "complexType": {
+            "original": "UtilityNetwork | undefined",
+            "resolved": "UtilityNetwork | undefined",
+            "references": {
+              "UtilityNetwork": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [
+            {
+              "name": "required"
+            }
+          ],
+          "values": [
+            {
+              "type": "UtilityNetwork"
+            },
+            {
+              "type": "undefined"
+            }
+          ],
+          "optional": false,
+          "required": true
+        }
+      ],
+      "methods": [
+        {
+          "name": "componentOnReady",
+          "returns": {
+            "type": "Promise<void>",
+            "docs": ""
+          },
+          "complexType": {
+            "signature": "(): Promise<void>",
+            "parameters": [],
+            "return": "Promise<void>",
+            "references": {
+              "Promise": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "signature": "componentOnReady(): Promise<void>",
+          "parameters": [],
+          "docs": "Create a promise that resolves once component is fully loaded.",
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\nconst arcgisResultFeatureList = document.querySelector(\"arcgis-result-feature-list\");\ndocument.body.append(arcgisResultFeatureList);\nawait arcgisResultFeatureList.componentOnReady();\nconsole.log(\"arcgis-result-feature-list is ready to go!\");\n```"
+            },
+            {
+              "name": "inheritedFrom",
+              "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+            }
+          ]
+        }
+      ],
+      "events": [
+        {
+          "event": "arcgisPropertyChange",
+          "detail": "{ name: \"selectedLayer\"; }",
+          "bubbles": true,
+          "complexType": {
+            "original": "{ name: \"selectedLayer\"; }",
+            "resolved": "{ name: \"selectedLayer\"; }",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "",
+          "docsTags": []
+        }
+      ],
+      "styles": [],
+      "slots": [],
+      "parts": [],
+      "listeners": []
+    },
+    {
+      "filePath": "src/components/utility-network-trace-analysis/components/utility-network-trace-inputs/utility-network-trace-inputs.tsx",
+      "tag": "arcgis-utility-network-trace-inputs",
+      "overview": "",
+      "readme": "",
+      "usage": {},
+      "docs": "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.",
+      "docsTags": [
+        {
+          "name": "since",
+          "text": "4.34"
+        },
+        {
+          "name": "internal"
+        },
+        {
+          "name": "superclass",
+          "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+        }
+      ],
+      "encapsulation": "shadow",
+      "dependents": [],
+      "dependencies": [],
+      "dependencyGraph": {},
+      "props": [
+        {
+          "name": "referenceElement",
+          "type": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+          "complexType": {
+            "original": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+            "resolved": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+            "references": {
+              "HTMLArcgisLinkChartElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              },
+              "HTMLArcgisMapElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              },
+              "HTMLArcgisSceneElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "attr": "reference-element",
+          "reflectToAttr": false,
+          "docs": "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.",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Associate components with a Map or Scene component](https://developers.arcgis.com/javascript/latest/programming-patterns/#associate-components-with-a-map-or-scene-component)"
+            }
+          ],
+          "values": [
+            {
+              "type": "HTMLArcgisLinkChartElement"
+            },
+            {
+              "type": "HTMLArcgisMapElement"
+            },
+            {
+              "type": "HTMLArcgisSceneElement"
+            },
+            {
+              "type": "string"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "selectedTraceConfiguration",
+          "type": "NamedTraceConfiguration",
+          "complexType": {
+            "original": "NamedTraceConfiguration",
+            "resolved": "NamedTraceConfiguration",
+            "references": {
+              "NamedTraceConfiguration": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "selectedUtilityNetwork",
+          "type": "UtilityNetwork",
+          "complexType": {
+            "original": "UtilityNetwork",
+            "resolved": "UtilityNetwork",
+            "references": {
+              "UtilityNetwork": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "view",
+          "type": "MapView | undefined",
+          "complexType": {
+            "original": "MapView | undefined",
+            "resolved": "MapView | undefined",
+            "references": {
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [
+            {
+              "name": "required"
+            }
+          ],
+          "values": [
+            {
+              "type": "MapView"
+            },
+            {
+              "type": "undefined"
+            }
+          ],
+          "optional": false,
+          "required": true
         }
       ],
       "methods": [
@@ -51659,46 +52534,23 @@
           "docsTags": [
             {
               "name": "example",
-              "text": "```js\nconst arcgisUtilityNetworkTraceAnalysis = document.querySelector(\"arcgis-utility-network-trace-analysis\");\ndocument.body.append(arcgisUtilityNetworkTraceAnalysis);\nawait arcgisUtilityNetworkTraceAnalysis.componentOnReady();\nconsole.log(\"arcgis-utility-network-trace-analysis is ready to go!\");\n```"
+              "text": "```js\nconst arcgisUtilityNetworkTraceInputs = document.querySelector(\"arcgis-utility-network-trace-inputs\");\ndocument.body.append(arcgisUtilityNetworkTraceInputs);\nawait arcgisUtilityNetworkTraceInputs.componentOnReady();\nconsole.log(\"arcgis-utility-network-trace-inputs is ready to go!\");\n```"
             },
             {
               "name": "inheritedFrom",
               "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
             }
           ]
-        },
-        {
-          "name": "destroy",
-          "returns": {
-            "type": "Promise<void>",
-            "docs": ""
-          },
-          "complexType": {
-            "signature": "(): Promise<void>",
-            "parameters": [],
-            "return": "Promise<void>",
-            "references": {
-              "Promise": {
-                "location": "import",
-                "path": "typescript/lib/lib.es5.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "signature": "destroy(): Promise<void>",
-          "parameters": [],
-          "docs": "Permanently destroy the component.",
-          "docsTags": []
         }
       ],
       "events": [
         {
-          "event": "arcgisPropertyChange",
-          "detail": "never",
+          "event": "arcgisTraceInputsChange",
+          "detail": "void",
           "bubbles": true,
           "complexType": {
-            "original": "never",
-            "resolved": "never",
+            "original": "void",
+            "resolved": "void",
             "references": {}
           },
           "cancelable": true,
@@ -51707,7 +52559,7 @@
           "docsTags": []
         },
         {
-          "event": "arcgisReady",
+          "event": "arcgisUtilityNetworkChange",
           "detail": "void",
           "bubbles": true,
           "complexType": {
@@ -51717,217 +52569,6 @@
           },
           "cancelable": true,
           "composed": true,
-          "docs": "Emitted when the component associated with a map or scene view is ready to be interacted with.",
-          "docsTags": []
-        }
-      ],
-      "styles": [],
-      "slots": [],
-      "parts": [],
-      "listeners": []
-    },
-    {
-      "filePath": "src/components/utility-network-trace-analysis/components/result-feature-list/result-feature-list.tsx",
-      "tag": "arcgis-result-feature-list",
-      "overview": "",
-      "readme": "",
-      "usage": {},
-      "docs": "This is a sub-component used by the **ArcgisUtilityNetworkTraceAnalysis** component.\n\nThis sub-component takes trace result elements as input.\nIt displays the layers the elements are from, with a count of elements on each layer.\nA `UtilityNetwork` and list of layers is required to display feature layer names.",
-      "docsTags": [
-        {
-          "name": "since",
-          "text": "4.34"
-        },
-        {
-          "name": "superclass",
-          "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
-        }
-      ],
-      "encapsulation": "shadow",
-      "dependents": [],
-      "dependencies": [],
-      "dependencyGraph": {},
-      "props": [
-        {
-          "name": "elements",
-          "type": "Array<NetworkElement>",
-          "complexType": {
-            "original": "Array<NetworkElement>",
-            "resolved": "Array<NetworkElement>",
-            "references": {
-              "Array": {
-                "location": "import",
-                "path": "typescript/lib/lib.es5.d.ts",
-                "id": "notImplemented"
-              },
-              "NetworkElement": {
-                "location": "import",
-                "path": "@arcgis/core/interfaces.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [
-            {
-              "name": "required"
-            }
-          ],
-          "values": [],
-          "optional": false,
-          "required": true
-        },
-        {
-          "name": "layers",
-          "type": "Array<Layer>",
-          "complexType": {
-            "original": "Array<Layer>",
-            "resolved": "Array<Layer>",
-            "references": {
-              "Array": {
-                "location": "import",
-                "path": "typescript/lib/lib.es5.d.ts",
-                "id": "notImplemented"
-              },
-              "Layer": {
-                "location": "import",
-                "path": "@arcgis/core/interfaces.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [
-            {
-              "name": "required"
-            }
-          ],
-          "values": [],
-          "optional": false,
-          "required": true
-        },
-        {
-          "name": "messageOverrides",
-          "type": "Record<string, unknown>",
-          "complexType": {
-            "original": "Record<string, unknown>",
-            "resolved": "Record<string, unknown>",
-            "references": {}
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
-          "values": [],
-          "optional": true,
-          "required": false
-        },
-        {
-          "name": "selectedLayer",
-          "type": "Layer",
-          "complexType": {
-            "original": "Layer",
-            "resolved": "Layer",
-            "references": {
-              "Layer": {
-                "location": "import",
-                "path": "@arcgis/core/interfaces.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
-          "values": [],
-          "optional": true,
-          "required": false
-        },
-        {
-          "name": "utilityNetwork",
-          "type": "UtilityNetwork | undefined",
-          "complexType": {
-            "original": "UtilityNetwork | undefined",
-            "resolved": "UtilityNetwork | undefined",
-            "references": {
-              "UtilityNetwork": {
-                "location": "import",
-                "path": "@arcgis/core/interfaces.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [
-            {
-              "name": "required"
-            }
-          ],
-          "values": [
-            {
-              "type": "UtilityNetwork"
-            },
-            {
-              "type": "undefined"
-            }
-          ],
-          "optional": false,
-          "required": true
-        }
-      ],
-      "methods": [
-        {
-          "name": "componentOnReady",
-          "returns": {
-            "type": "Promise<void>",
-            "docs": ""
-          },
-          "complexType": {
-            "signature": "(): Promise<void>",
-            "parameters": [],
-            "return": "Promise<void>",
-            "references": {
-              "Promise": {
-                "location": "import",
-                "path": "typescript/lib/lib.es5.d.ts",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "signature": "componentOnReady(): Promise<void>",
-          "parameters": [],
-          "docs": "Create a promise that resolves once component is fully loaded.",
-          "docsTags": [
-            {
-              "name": "example",
-              "text": "```js\nconst arcgisResultFeatureList = document.querySelector(\"arcgis-result-feature-list\");\ndocument.body.append(arcgisResultFeatureList);\nawait arcgisResultFeatureList.componentOnReady();\nconsole.log(\"arcgis-result-feature-list is ready to go!\");\n```"
-            },
-            {
-              "name": "inheritedFrom",
-              "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
-            }
-          ]
-        }
-      ],
-      "events": [
-        {
-          "event": "arcgisPropertyChange",
-          "detail": "{ name: \"selectedLayer\"; }",
-          "bubbles": true,
-          "complexType": {
-            "original": "{ name: \"selectedLayer\"; }",
-            "resolved": "{ name: \"selectedLayer\"; }",
-            "references": {}
-          },
-          "cancelable": true,
-          "composed": true,
           "docs": "",
           "docsTags": []
         }
@@ -52015,7 +52656,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -52169,7 +52810,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology-UtilityNetworkValidateTopologyViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -52244,7 +52885,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "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)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -52602,7 +53243,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -53233,8 +53874,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "values": [
             {
               "type": "string"
@@ -53462,7 +54108,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VersionManagement-VersionManagementViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -54248,7 +54894,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the video layer.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VideoPlayer-VideoPlayerViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -54742,7 +55388,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -55130,7 +55776,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {