@arcgis/map-components 5.0.0-next.22 → 5.0.0-next.24

package/dist/docs/docs.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-10-15T04:45:55",
+  "timestamp": "2025-10-17T04:45:30",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "5.0.0-next.22",
+    "version": "5.0.0-next.24",
     "typescriptVersion": "5.8.3"
   },
   "components": [
@@ -386,7 +386,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -910,7 +910,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -2150,7 +2150,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Gallery component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -3219,7 +3219,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Layer List component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -3745,7 +3745,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Toggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -3992,7 +3992,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Specifies how new bookmarks will be created if [showAddBookmarkButton](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-bookmarks/#showAddBookmarkButton) is set to `true`.\nCan be used to enable or disable taking screenshots or capturing the bookmark's viewpoint based on the current\nview when a bookmark is created. See [BookmarkOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel-BookmarkOptions.html)\nfor the full list of options.",
+          "docs": "Specifies how new bookmarks will be created if [showAddBookmarkButton](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-bookmarks/#showAddBookmarkButton) is set to `true`.\nCan be used to enable or disable taking screenshots or capturing the bookmark's viewpoint based on the current\nview when a bookmark is created. See [BookmarkOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#BookmarkOptions)\nfor the full list of options.",
           "docsTags": [
             {
               "name": "example",
@@ -4019,7 +4019,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Specifies how bookmarks will be edited, if [showEditBookmarkButton](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-bookmarks/#showEditBookmarkButton) is set to `true`.\nCan be used to enable or disable taking screenshots or capturing the bookmark's viewpoint based on the current\nview when a bookmark is edited. See [BookmarkOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel-BookmarkOptions.html)\nfor the full list of options.",
+          "docs": "Specifies how bookmarks will be edited, if [showEditBookmarkButton](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-bookmarks/#showEditBookmarkButton) is set to `true`.\nCan be used to enable or disable taking screenshots or capturing the bookmark's viewpoint based on the current\nview when a bookmark is edited. See [BookmarkOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#BookmarkOptions)\nfor the full list of options.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -4161,6 +4161,10 @@
               "name": "see",
               "text": "[Heading Elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)"
             },
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "example",
               "text": "```js\n// \"No bookmarks\" will render as an <h3>\nbookmarksElement.headingLevel = 3;\n```"
@@ -4336,7 +4340,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -4689,7 +4698,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Bookmarks component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -4797,7 +4806,12 @@
             }
           ],
           "docs": "Zoom to a specific bookmark.",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         }
       ],
       "events": [
@@ -4818,8 +4832,12 @@
           },
           "cancelable": true,
           "composed": true,
-          "docs": "\nFires when a [Bookmark](https://developers.arcgis.com/javascript/latest/api-reference/esri-webmap-Bookmark.html) is edited.",
+          "docs": "Fires when a [Bookmark](https://developers.arcgis.com/javascript/latest/api-reference/esri-webmap-Bookmark.html) is edited.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "example",
               "text": "```js\n// once an edit has been made, enable the \"Save Webmap\" button\n//    to allow the user to save their changes\nbookmarksElement.addEventListener(\"arcgisBookmarkEdit\", (event) => {\n   saveBtn.disabled = false;\n});\n```"
@@ -4845,6 +4863,10 @@
           "composed": true,
           "docs": "Fires when a [Bookmark](https://developers.arcgis.com/javascript/latest/api-reference/esri-webmap-Bookmark.html) is selected.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "example",
               "text": "```html\n<arcgis-expand expanded>\n <arcgis-bookmarks></arcgis-bookmarks>\n</arcgis-expand>\n```\n\n```js\nconst bookmarksElement = document.querySelector(\"arcgis-bookmarks\");\nconst expandElement = document.querySelector(\"arcgis-expand\");\n\n// collapses the associated Expand component\n// when a bookmark is selected\nbookmarksElement.addEventListener(\"arcgisBookmarkSelect\", (event) => {\n  expandElement.expanded = false;\n});\n```"
@@ -5322,7 +5344,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Building Explorer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -6140,7 +6162,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Catalog Layer List component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -6632,7 +6654,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Compass component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -7568,7 +7590,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Coordinate Conversion component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -7767,8 +7789,24 @@
       "overview": "",
       "readme": "",
       "usage": {},
-      "docs": "The Daylight component can be used to manipulate the lighting conditions of a\n[Scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/).\nFor this, the component modifies the `lighting` property of the\n[environment](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment) of the Scene component.\n\nTo illuminate the scene, one can either use a configuration of date and time to position the\n[sun](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html) or switch to the\n[virtual mode](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html) mode,\nwhere the light source is relative to the camera.\n\nWhen **lighting the scene with the sun** and adjusting the time and date, the position of the sun\nand the stars get updated accordingly, changing the light and the shadows in the scene. This sets the `date` and `directShadowsEnabled` properties of\n[environment.lighting](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment).\n\n[![daylight-default](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-default.png)](https://developers.arcgis.com/javascript/latest/sample-code/daylight/)\n\nThe component has an option to select the timezone. When the user makes any adjustments here, a new time\nin the chosen timezone is calculated and displayed in the slider. The timezone selector can be disabled\nby using `hide-timezone` attribute or setting `hideTimezone` property to `true`.\n\nBy default, a calendar is displayed where the user can select the day, month and year.\nWith the [dateOrSeason](#dateOrSeason) property, the calendar can be replaced with\na dropdown menu where a season can be selected instead:\n\n![daylight-seasons](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-seasons.png)\n\nThere are two play buttons, one corresponds to the daytime slider and it animates the time as\nit cycles through the minutes of the day. The second button corresponds to the date picker\nand it animates the time as it cycles through the months of the year. The speed of the animation can\nbe set using the [playSpeedMultiplier](#playSpeedMultiplier) property.\n\n![daylight-animation](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-animation.gif)\n\nExcept for the daytime slider, all the elements in the Daylight component can be hidden:\n\n![daylight-no-elements](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-no-elements.png)\n\nWhenever the sun position option is unchecked, the scene applies the **virtual light source** relative to the camera.\nWith this, the component's time slider, timezone and date picker get automatically disabled:\n\n![daylight-virtual](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-virtual.png)\n\n**Things to consider**\n\n* Daylight is only supported in a 3D [Scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) component.\n* The Daylight component uses UTC time and does not account for the daylight savings times in different countries and regions of the world.\n* When the [environment.lighting](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment)\nis of the type `virtual`, setting the time and date does not have an influence on the lighting conditions of the scene.\n\n**See also**\n\n- [Environment](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment)\n- [SunLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html)\n- [VirtualLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html)\n- [Sample - Daylight component](https://developers.arcgis.com/javascript/latest/sample-code/daylight/)",
+      "docs": "The Daylight component can be used to manipulate the lighting conditions of a\n[Scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/).\nTo achieve this, the component modifies the `lighting` property of the\n[environment](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment) of the Scene component.\n\nTo illuminate the scene, one can either use a configuration of date and time to position the\n[sun](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html) or switch to the\n[virtual](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html) mode,\nwhere the light source is relative to the camera.\n\nWhen illuminating the scene with **[sunlight](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html)**\nand adjusting the time and date, the positions of the sun and stars are updated accordingly. This also updates the\n[date](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html#date) property of\n[environment.lighting](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment).\n\n[![daylight-default](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-default.png)](https://developers.arcgis.com/javascript/latest/sample-code/daylight/)\n\nThe component has an option to select the timezone. When the user makes any adjustments here, a new time\nin the chosen timezone is calculated and displayed in the slider. The timezone selector can be disabled\nby using the [hideTimezone](#hideTimezone) property.\n\nBy default, a calendar is displayed to select the day, month, and year.\nWith the [dateOrSeason](#dateOrSeason) property, the calendar can be replaced with\na dropdown menu where a season can be selected instead:\n\n![daylight-seasons](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-seasons.png)\n\nThere are two play buttons: one corresponds to the time-of-day slider and animates the lighting\nover the course of a day, while the other corresponds to the date picker\nand animates the lighting over the course of a year (month by month). The speed of the animation can\nbe set using the [playSpeedMultiplier](#playSpeedMultiplier) property.\n\n![daylight-animation](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-animation.gif)\n\nExcept for the daytime slider, all the elements in the Daylight component can be hidden:\n\n![daylight-no-elements](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-no-elements.png)\n\nWhenever the sun position option is unchecked, the scene applies the\n**[virtual light](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html)** source relative to the camera.\nWith this, the component's time slider, timezone, and date picker get automatically disabled:\n\n![daylight-virtual](https://developers.arcgis.com/javascript/latest/assets/img/apiref/components/daylight/daylight-virtual.png)\n\n**Things to consider**\n\n* Daylight is only supported in a 3D [Scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) component.\n* The Daylight component uses UTC time and does not account for the daylight savings times in different countries and regions of the world.\n* When using the [virtual light](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html),\nsetting the time and date programmatically does not have an influence on the lighting conditions of the scene.\n* When using the [sunlight](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html),\nthe time slider and time zone automatically react to the changes of the camera (e.g., position, rotation, pan, zoom) because the position of the simulated sun\nis updated to maintain a consistent solar time of day based on the camera's current longitude. This can be adjusted using the\n[cameraTrackingEnabled](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html#cameraTrackingEnabled)\nproperty on [environment.lighting](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment).",
       "docsTags": [
+        {
+          "name": "see",
+          "text": "[Environment](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment)"
+        },
+        {
+          "name": "see",
+          "text": "[SunLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html)"
+        },
+        {
+          "name": "see",
+          "text": "[VirtualLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html)"
+        },
+        {
+          "name": "see",
+          "text": "[Sample - Daylight component](https://developers.arcgis.com/javascript/latest/sample-code/daylight/)"
+        },
         {
           "name": "since",
           "text": "4.28"
@@ -7816,8 +7854,13 @@
           "mutable": true,
           "attr": "current-season",
           "reflectToAttr": false,
-          "docs": "Sets the season that is used when the component displays a season picker.\nEach season uses a fixed date corresponding to the seasonal equinoxes and solstices.\n\n**See also**\n\n[dateOrSeason](#dateOrSeason)",
-          "docsTags": [],
+          "docs": "Sets the season that is used when the component displays the season picker.\nEach season uses a fixed date corresponding to the seasonal equinoxes and solstices.",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[dateOrSeason](#dateOrSeason)"
+            }
+          ],
           "values": [
             {
               "value": "fall",
@@ -7888,28 +7931,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "directShadowsDisabled",
-          "type": "boolean",
-          "complexType": {
-            "original": "boolean",
-            "resolved": "boolean",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "direct-shadows-disabled",
-          "reflectToAttr": false,
-          "docs": "Indicates whether to hide shadows cast by the sun.\n\n**See also**\n\n- [SunLighting.directShadowsEnabled](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html#directShadowsEnabled)\n- [Scene's `environment`](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#environment)",
-          "docsTags": [],
-          "default": "false",
-          "values": [
-            {
-              "type": "boolean"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
         {
           "name": "headingLevel",
           "type": "1 | 2 | 3 | 4 | 5 | 6",
@@ -8096,8 +8117,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": true,
-          "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. Typically 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": "\"brightness\"",
           "values": [
             {
@@ -8146,45 +8172,28 @@
           "attr": "local-date",
           "reflectToAttr": false,
           "docs": "The calendar date in the timezone given by [utcOffset](#utcOffset).",
-          "docsTags": [],
-          "values": [
+          "docsTags": [
             {
-              "type": "Date"
+              "name": "example",
+              "text": "```js\ndaylight.localDate = new Date(\"2005-08-25\");\n```"
             },
             {
-              "type": "number"
+              "name": "example",
+              "text": "```js\n// Alternatively, the date can be set by configuring the `date` property of `SunLighting`.\nviewElement.environment.lighting = new SunLighting({\n  date: new Date(\"2005-08-25T16:00:00\")\n});\n```"
             },
             {
-              "type": "string"
+              "name": "since",
+              "text": "4.34"
             }
           ],
-          "optional": true,
-          "required": false
-        },
-        {
-          "name": "playingState",
-          "type": "\"day\" | \"none\" | \"year\"",
-          "complexType": {
-            "original": "\"day\" | \"none\" | \"year\"",
-            "resolved": "\"day\" | \"none\" | \"year\"",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "playing-state",
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
           "values": [
             {
-              "value": "day",
-              "type": "string"
+              "type": "Date"
             },
             {
-              "value": "none",
-              "type": "string"
+              "type": "number"
             },
             {
-              "value": "year",
               "type": "string"
             }
           ],
@@ -8206,7 +8215,7 @@
           "docsTags": [
             {
               "name": "example",
-              "text": "// Plays the daylight animation at half of the default speed\ndaylight.playSpeedMultiplier = 0.5;"
+              "text": "```js\n// Plays the daylight animation at half of the default speed\ndaylight.playSpeedMultiplier = 0.5;\n```"
             }
           ],
           "default": "1.0",
@@ -8324,54 +8333,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "sunlightingDisabled",
-          "type": "boolean",
-          "complexType": {
-            "original": "boolean",
-            "resolved": "boolean",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "sunlighting-disabled",
-          "reflectToAttr": false,
-          "docs": "When set, the light source is positioned relative to the camera, using\n[VirtualLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-VirtualLighting.html).\nOtherwise, [date and time](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html)\nare used to determine position of the light source.",
-          "docsTags": [],
-          "default": "false",
-          "values": [
-            {
-              "type": "boolean"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
-        {
-          "name": "supported",
-          "type": "boolean",
-          "complexType": {
-            "original": "boolean",
-            "resolved": "boolean",
-            "references": {}
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [
-            {
-              "name": "readonly",
-              "text": ""
-            }
-          ],
-          "default": "false",
-          "values": [
-            {
-              "type": "boolean"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
         {
           "name": "timeSliderPosition",
           "type": "number",
@@ -8387,7 +8348,15 @@
           "docsTags": [
             {
               "name": "example",
-              "text": "viewElement.environment.lighting = new SunLighting({\n  date: new Date(\"2022-06-21T12:00:00\")\n});"
+              "text": "```js\n// Set the time to 4:00 PM (16:00) in the given timezone.\ndaylight.timeSliderPosition = 16 * 60;\n```"
+            },
+            {
+              "name": "example",
+              "text": "```js\n// Alternatively, the time can be set by configuring the `date` property of `SunLighting`.\n// Then, the time slider gets updated automatically.\nviewElement.environment.lighting = new SunLighting({\n  date: new Date(\"2005-08-25T16:00:00\")\n});\n```"
+            },
+            {
+              "name": "since",
+              "text": "4.34"
             }
           ],
           "values": [
@@ -8400,19 +8369,33 @@
         },
         {
           "name": "timeSliderSteps",
-          "type": "number",
+          "type": "Array<number> | number",
           "complexType": {
-            "original": "number",
-            "resolved": "number",
-            "references": {}
+            "original": "Array<number> | number",
+            "resolved": "Array<number> | number",
+            "references": {
+              "Array": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              }
+            }
           },
           "mutable": true,
           "attr": "time-slider-steps",
           "reflectToAttr": false,
-          "docs": "Sets the interval, in minutes, with which the time slider increments or decrements as it is dragged or changed via the keyboard.\n\nFor example, if set to 60, the slider will allow selecting each hour of the day.",
-          "docsTags": [],
+          "docs": "Sets the interval, in minutes, with which the time slider increments or decrements as it is dragged or changed via the keyboard.",
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\n// Set steps at an interval of 60. Then, the slider thumb snaps at each hour of the day.\ndaylight.timeSliderSteps = 60;\n```"
+            }
+          ],
           "default": "5",
           "values": [
+            {
+              "type": "Array<number>"
+            },
             {
               "type": "number"
             }
@@ -8432,7 +8415,20 @@
           "attr": "utc-offset",
           "reflectToAttr": false,
           "docs": "The difference in hours between UTC time and the time displayed in the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\ndaylight.utcOffset = -8;\n```"
+            },
+            {
+              "name": "example",
+              "text": "```js\n// Alternatively, the UTC offset can be set by configuring the `displayUTCOffset` property of `SunLighting`.\nviewElement.environment.lighting = new SunLighting({\n  displayUTCOffset: -8\n});\n```"
+            },
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [
             {
               "type": "number"
@@ -8443,21 +8439,11 @@
         },
         {
           "name": "view",
-          "type": "LinkChartView | MapView | SceneView",
+          "type": "SceneView",
           "complexType": {
-            "original": "LinkChartView | MapView | SceneView",
-            "resolved": "LinkChartView | MapView | SceneView",
+            "original": "SceneView",
+            "resolved": "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",
@@ -8469,17 +8455,7 @@
           "reflectToAttr": false,
           "docs": "",
           "docsTags": [],
-          "values": [
-            {
-              "type": "LinkChartView"
-            },
-            {
-              "type": "MapView"
-            },
-            {
-              "type": "SceneView"
-            }
-          ],
+          "values": [],
           "optional": true,
           "required": false
         },
@@ -8956,7 +8932,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directional Pad component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -9691,7 +9667,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directions component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -10293,7 +10269,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -10806,7 +10782,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Distance Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -11651,7 +11627,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Editor component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -11986,7 +11962,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when a user starts drawing a feature, is actively drawing a feature, and completes drawing a feature.",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisSketchUpdate",
@@ -12006,7 +11987,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when a user starts updating a feature's geometry, is actively updating a feature's geometry, and completes updating a feature's geometry.",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         }
       ],
       "styles": [],
@@ -12731,7 +12717,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -13744,7 +13730,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile Next component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -14282,7 +14268,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -14539,6 +14530,10 @@
           "reflectToAttr": true,
           "docs": "The current state of the component.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -14579,7 +14574,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Expand component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -14832,48 +14827,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "flowItems",
-          "type": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureUtilityNetworkAssociationsElement>",
-          "complexType": {
-            "original": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureUtilityNetworkAssociationsElement>",
-            "resolved": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureUtilityNetworkAssociationsElement>",
-            "references": {
-              "Collection": {
-                "location": "import",
-                "path": "@arcgis/core/interfaces.d.ts",
-                "id": "notImplemented"
-              },
-              "HTMLArcgisFeatureElement": {
-                "location": "local",
-                "path": "index.js",
-                "id": "notImplemented"
-              },
-              "HTMLArcgisFeatureRelationshipElement": {
-                "location": "local",
-                "path": "index.js",
-                "id": "notImplemented"
-              },
-              "HTMLArcgisFeatureUtilityNetworkAssociationsElement": {
-                "location": "local",
-                "path": "index.js",
-                "id": "notImplemented"
-              }
-            }
-          },
-          "mutable": true,
-          "reflectToAttr": false,
-          "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
-        },
         {
           "name": "graphic",
           "type": "Graphic",
@@ -15011,7 +14964,12 @@
           "attr": "hide-attachments-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [attachments content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15202,7 +15160,12 @@
           "attr": "hide-expression-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [expression content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15224,7 +15187,12 @@
           "attr": "hide-fields-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [fields content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15318,7 +15286,12 @@
           "attr": "hide-media-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [media content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15340,7 +15313,12 @@
           "attr": "hide-text-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [text content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15523,7 +15501,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Overwrite localized strings for this component.",
+          "docs": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
           "docsTags": [
             {
               "name": "since",
@@ -15678,7 +15656,7 @@
           "mutable": true,
           "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.",
+          "docs": "This property provides the ability to hide or show [utility network content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkAssociationsContent.html) within the component.",
           "docsTags": [
             {
               "name": "since",
@@ -15811,7 +15789,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -15841,7 +15819,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -15970,7 +15953,7 @@
               "docs": ""
             }
           ],
-          "docs": "Paginates to the previous [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info in the specified\n[media](esri-popup-content-MediaContent.html) content element.",
+          "docs": "Paginates to the previous [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info.",
           "docsTags": []
         },
         {
@@ -16015,7 +15998,7 @@
               "docs": ""
             }
           ],
-          "docs": "Paginates to a specified [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info object. For example,\nyou may have [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) content which contains\nmultiple `mediaInfos`. This method allows you to specify the index of the `mediaInfos`\nyou wish to display.\n\n::: esri-md class=\"warning\"\nPrior to   version 4.17, this method was named `goToMedia`.\n:::",
+          "docs": "Paginates to a specified [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) info object. For example,\nyou may have [media](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html) content which contains\nmultiple `mediaInfos`. This method allows you to specify the index of the `mediaInfos`\nyou wish to display.",
           "docsTags": []
         },
         {
@@ -19223,7 +19206,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature Table component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -20793,7 +20776,12 @@
           "attr": "default-popup-template-enabled",
           "reflectToAttr": false,
           "docs": "Enables automatic creation of a popup template for layers that have popups enabled but no\npopupTemplate defined.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#defaultPopupTemplateEnabled)",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -20872,7 +20860,12 @@
           "attr": "feature-menu-title",
           "reflectToAttr": false,
           "docs": "Sets the title to display on the component while viewing the feature menu.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [
             {
               "type": "string"
@@ -21084,6 +21077,10 @@
               "name": "see",
               "text": "[headingLevel](#headingLevel)"
             },
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "example",
               "text": "```js\n// This title will display in the component unless a selected feature's\n// PopupTemplate overrides it.\nfeaturesComponent.title = \"Population by zip codes in Southern California\";\n```"
@@ -21196,7 +21193,12 @@
           "attr": "hide-feature-list-layer-title",
           "reflectToAttr": false,
           "docs": "Indicates whether to hide the group heading for a list of multiple features.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -21381,7 +21383,12 @@
           "attr": "include-default-actions-disabled",
           "reflectToAttr": false,
           "docs": "Indicates whether to include the default actions in the component.\nIn order to disable any default actions, it is necessary to set `includeDefaultActionsDisabled` to `true`.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -21489,7 +21496,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -21908,7 +21920,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -21925,7 +21942,12 @@
           "attr": "visible",
           "reflectToAttr": false,
           "docs": "Indicates whether the popup is visible. This property is `true` when the popup is querying for results, even if it is not open in the view.\nUse the property to check if the component is visible.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -22243,7 +22265,12 @@
           "signature": "setFocus(): Promise<void>",
           "parameters": [],
           "docs": "Use this method to give focus to the Component if the component is able to be focused.",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "name": "triggerAction",
@@ -22703,7 +22730,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Floor Filter component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -24055,7 +24082,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Grid Controls component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -25205,7 +25232,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Home component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -26305,7 +26332,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Layer List component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -26544,7 +26571,7 @@
       "overview": "",
       "readme": "",
       "usage": {},
-      "docs": "The Legend component displays the symbols and labels used to represent layers in a [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/).\nOnly layers and sublayers visible in the view are shown, unless [ignoreLayerVisibility](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-legend/#ignoreLayerVisibility) is set to `true`.\n\nThe legend automatically updates when:\n - the visibility of a layer or sublayer changes\n - a layer is added or removed from the map\n - a layer's `renderer`, `opacity`, or `title` is changed\n - the `legendEnabled` property is changed (set to `true` or `false` on the layer)\n\n## Known Limitations\n\n* Currently, the legend component does not support the following layer types:\n[ElevationLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-ElevationLayer.html),\n[GraphicsLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GraphicsLayer.html),\n[IntegratedMeshLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-IntegratedMeshLayer.html),\n[KMLLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-KMLLayer.html),\n[MapNotesLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-MapNotesLayer.html),\n[OpenStreetMapLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-OpenStreetMapLayer.html),\n[VectorTileLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VectorTileLayer.html),\n[VideoLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VideoLayer.html), and\n[WebTileLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-WebTileLayer.html).\n* [Symbol3D](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-Symbol3D.html) with more than one\n[symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-Symbol3DLayer.html) are not supported.\n* [DictionaryRenderer](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-DictionaryRenderer.html) is not supported.\n* [TrackInfo](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-TrackInfo.html) is not supported.\n* CIM Symbol [primitiveOverride](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-CIMSymbol.html#PrimitiveOverride) is not supported.\n* RasterStretchRenderer [dynamicRangeAdjustment](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-RasterStretchRenderer.html#dynamicRangeAdjustment) is not supported.\n\n## Various examples of legends based on renderer type.\n\n### Unique values\n\n[![Unique values](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-unique-values.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-location-types/)\n\n### Continuous color\n\n[![Continuous color](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-color-vv.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-vv-color/)\n\n### Classed color\n\n[![Classed color](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-class-breaks.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-classbreaks/)\n\n### Continuous size\n\n[![Continuous size](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-size.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-size/)\n\n### Size - above and below\n\n[![Size - above and below](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-size-themes.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-size-themes/)\n\n### Dot density\n\n[![Dot density](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-dot-density.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-dot-density/)\n\n### Predominance\n\n[![Predominance](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-predominance.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-arcade/)\n\n### Relationship\n\n[![Relationship](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-relationship.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-relationship/)\n\n\n### Legend Field Formatting Summary\n\nThe following table summarizes how legend field values are formatted for different renderer and visual variable types, and the order in which formatting options are applied.\n\n| Renderer / Visual Variable Type              | Renderer Data Source                   | Formatting Priority (in order)                                                                                                             |\n|----------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|\n| Visual variable stops (color, opacity, size) | Number field                           | 1. `stop.label`<br>2. FieldConfiguration<br>3. Default precision formatting with grouping                                                  |\n| Visual variable stops (color, opacity, size) | Number field / normalization field     | 1. `stop.label`<br>2. FieldConfiguration (applies to main field, not normalization field)<br>3. Default precision formatting with grouping |\n| Visual variable                              | valueExpression                        | 1. `stop.label`<br>2. Default precision formatting with grouping                                                                           |\n| Unique-value renderer labels                 | Field value                            | 1. UniqueValueRenderer class label<br>2. Domain name<br>3. FieldConfiguration or PopupTemplate<br>4. Raw field value (if string) or default precision formatting with grouping (for number)|\n| Renderer title                               | FieldConfiguration or PopupTemplate    | 1. FieldConfiguration<br>2. PopupTemplate                                                                                                  |\n\n#### Legend Field Formatting Notes\n- [FieldConfiguration](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FieldConfiguration.html): Defines how fields in a layer are displayed and formatted within widgets and UI components.\n- [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html): Used as a fallback for layers that don’t support FieldConfigurations.\n- VisualVariable stop labels: If any stop has a label, it is used directly; otherwise, labels are generated at runtime. See [ColorStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-ColorStop.html), [OpacityStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-OpacityStop.html), and [SizeStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-SizeStop.html).\n- Normalization Field: Only the main field’s formatting is used, not the normalization field. See [ColorVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-ColorVariable.html#normalizationField), [OpacityVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-OpacityVariable.html#normalizationField), and [SizeVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-SizeVariable.html#normalizationField).\n- [VisualVariable value expressions](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-ColorVariable.html#valueExpression): Since there’s no field, field formatting does not apply; fallback is default formatting.\n- WebMap and Layer persistence: Labels generated at runtime by the legend are not persisted.",
+      "docs": "The Legend component displays the symbols and labels used to represent layers in a [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/).\nOnly layers and sublayers visible in the view are shown, unless [ignoreLayerVisibility](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-legend/#ignoreLayerVisibility) is set to `true`.\n\nThe legend automatically updates when:\n - the visibility of a layer or sublayer changes\n - a layer is added or removed from the map\n - a layer's `renderer`, `opacity`, or `title` is changed\n - the `legendEnabled` property is changed (set to `true` or `false` on the layer)\n\n## Known Limitations\n\n* Currently, the legend component does not support the following layer types:\n[ElevationLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-ElevationLayer.html),\n[GraphicsLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GraphicsLayer.html),\n[IntegratedMeshLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-IntegratedMeshLayer.html),\n[KMLLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-KMLLayer.html),\n[MapNotesLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-MapNotesLayer.html),\n[OpenStreetMapLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-OpenStreetMapLayer.html),\n[VectorTileLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VectorTileLayer.html),\n[VideoLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VideoLayer.html), and\n[WebTileLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-WebTileLayer.html).\n* [Symbol3D](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-Symbol3D.html) with more than one\n[symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-Symbol3DLayer.html) are not supported.\n* [DictionaryRenderer](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-DictionaryRenderer.html) is not supported.\n* [TrackInfo](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-TrackInfo.html) is not supported.\n* CIM Symbol [primitiveOverride](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-CIMSymbol.html#PrimitiveOverride) is not supported.\n* RasterStretchRenderer [dynamicRangeAdjustment](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-RasterStretchRenderer.html#dynamicRangeAdjustment) is not supported.\n\n## Various examples of legends based on renderer type.\n\n### Unique values\n\n[![Unique values](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-unique-values.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-location-types/)\n\n### Continuous color\n\n[![Continuous color](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-color-vv.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-vv-color/)\n\n### Classed color\n\n[![Classed color](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-class-breaks.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-classbreaks/)\n\n### Continuous size\n\n[![Continuous size](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-size.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-size/)\n\n### Size - above and below\n\n[![Size - above and below](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-size-themes.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-size-themes/)\n\n### Dot density\n\n[![Dot density](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-dot-density.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-dot-density/)\n\n### Predominance\n\n[![Predominance](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-predominance.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-arcade/)\n\n### Relationship\n\n[![Relationship](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/legend/legend-relationship.png)](https://developers.arcgis.com/javascript/latest/sample-code/visualization-sm-relationship/)\n\n\n## Legend Field Formatting Priority\n\nThe following list summarizes how legend field values are formatted for different renderer and visual variable types, and the order in which formatting options are applied.\n\n * **Visual variable stops (color, opacity, size)**\n   * Data source:\n     * Number field\n       1. Use `stop.label` if present\n       2. Use [FieldConfiguration](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FieldConfiguration.html) formatting\n       3. Use default precision formatting with grouping\n     * Number field with normalization field\n       1. Use `stop.label` if present\n       2. Use FieldConfiguration (applies to main field, not normalization field)\n       3. Use default precision formatting with grouping\n   * Notes:\n     * If any stop has a label, it is used directly; otherwise, labels are generated at runtime. See [ColorStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-ColorStop.html), [OpacityStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-OpacityStop.html), and [SizeStop](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-support-SizeStop.html).\n     * For normalization fields, only the main field’s formatting is used, not the normalization field. See [ColorVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-ColorVariable.html#normalizationField), [OpacityVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-OpacityVariable.html#normalizationField), and [SizeVariable](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-SizeVariable.html#normalizationField).\n * **Visual variable (valueExpression)**\n   1. Use `stop.label` if present\n   2. Use default precision formatting with grouping\n   * Note: Since there’s no field, field formatting does not apply; fallback is default formatting. See [VisualVariable value expressions](https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-ColorVariable.html#valueExpression).\n * **Unique-value renderer labels**\n   1. Use UniqueValueRenderer class label if present\n   2. Use domain name\n   3. Use FieldConfiguration formatting\n   4. Use [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) formatting\n   5. Use raw field value (if string) or default precision formatting with grouping (for number)\n * **Renderer title**\n   1. Use FieldConfiguration formatting\n   2. Use PopupTemplate formatting\n * **General notes**\n   * Labels generated at runtime by the legend are not persisted in the WebMap or Layer.",
       "docsTags": [
         {
           "name": "see",
@@ -26975,8 +27002,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Overwrite localized strings for this component",
-          "docsTags": [],
+          "docs": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -27207,7 +27239,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Legend component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -27604,7 +27636,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Line Of Sight component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -27871,7 +27903,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "A collection of analyses associated with the view.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#analyses)",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -29434,7 +29471,12 @@
             }
           ],
           "docs": "Gets the analysis view created for the given analysis object.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#whenAnalysisView)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "name": "whenLayerView",
@@ -29528,7 +29570,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when the view for an analysis is created.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-create)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewAnalysisViewCreateError",
@@ -29548,7 +29595,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when an error occurs during the creation of an analysis view after an analysis is added to the view.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-create-error)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewAnalysisViewDestroy",
@@ -29568,7 +29620,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires after an analysis view is destroyed.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-destroy)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewChange",
@@ -30430,7 +30487,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Link Chart Layout Switcher component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -30988,7 +31045,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Locate component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -31249,7 +31306,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "A collection of analyses associated with the view.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#analyses)",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -33237,7 +33299,12 @@
             }
           ],
           "docs": "Gets the analysis view created for the given analysis object.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#whenAnalysisView)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "name": "whenLayerView",
@@ -33331,7 +33398,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when the view for an analysis is created.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-create)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewAnalysisViewCreateError",
@@ -33351,7 +33423,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires when an error occurs during the creation of an analysis view after an analysis is added to the view.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-create-error)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewAnalysisViewDestroy",
@@ -33371,7 +33448,12 @@
           "cancelable": true,
           "composed": true,
           "docs": "Fires after an analysis view is destroyed.\n\n[Read more](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#event-analysis-view-destroy)",
-          "docsTags": []
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         },
         {
           "event": "arcgisViewChange",
@@ -34369,7 +34451,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Measurement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -34813,7 +34895,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Navigation Toggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -35447,7 +35529,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Oriented Imagery Viewer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -35708,7 +35790,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Placement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -36954,7 +37036,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPopup component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Popup component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -38176,7 +38258,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Print component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -38602,7 +38684,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Bar component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -39157,7 +39239,12 @@
           "attr": "show-world-value",
           "reflectToAttr": false,
           "docs": "Indicates whether the world scale value is shown in the scale menu.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -39220,7 +39307,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Range Slider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -43077,7 +43164,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Search component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -44256,7 +44343,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Shadow Cast component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -45676,7 +45763,7 @@
           "mutable": true,
           "attr": "toolbar-kind",
           "reflectToAttr": false,
-          "docs": "Controls the appearance of the sketch widget, allowing\nthe toolbar to adapt its appearance appropriately based on context.",
+          "docs": "Controls the appearance of the sketch widget, allowing the toolbar to adapt its appearance appropriately based on context.\n\nSet this to `docked` for use within the Expand component, or any other situation\nwhere Sketch is not floating within a large canvas.",
           "docsTags": [],
           "default": "\"floating\"",
           "values": [
@@ -45767,7 +45854,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Sketch component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -46666,7 +46753,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Slice component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -47243,7 +47330,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Swipe component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -47692,7 +47779,12 @@
           "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": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [
             {
               "type": "Map"
@@ -48142,7 +48234,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Table List component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -48896,7 +48988,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Time Slider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -49294,6 +49386,10 @@
           "reflectToAttr": true,
           "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "see",
               "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
@@ -50060,7 +50156,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Track component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -50351,7 +50447,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-color-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association color picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50373,7 +50469,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-style-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association style picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50395,7 +50491,7 @@
           "mutable": true,
           "attr": "hide-connectivity-associations-settings-width-input",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the connectivity association width input.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50417,7 +50513,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-color-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations color picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50439,7 +50535,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-style-picker",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations style picker.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50461,7 +50557,7 @@
           "mutable": true,
           "attr": "hide-structural-attachment-associations-settings-width-input",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the structural attachment associations width input.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50832,7 +50928,7 @@
           "mutable": true,
           "attr": "show-connectivity-associations-settings-arrows-toggle",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the connectivity association arrows toggle.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50854,7 +50950,7 @@
           "mutable": true,
           "attr": "show-connectivity-associations-settings-cap-select",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the connectivity association cap select.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50876,7 +50972,7 @@
           "mutable": true,
           "attr": "show-max-allowable-associations-slider",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, hides the max allowable associations slider.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50898,7 +50994,7 @@
           "mutable": true,
           "attr": "show-structural-attachment-associations-settings-arrows-toggle",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the structural attachment associations arrow toggle.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50920,7 +51016,7 @@
           "mutable": true,
           "attr": "show-structural-attachment-associations-settings-cap-select",
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "If true, shows the structural attachment associations cap select.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -50991,7 +51087,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Associations component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -51011,7 +51107,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead",
+          "deprecation": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead.",
           "values": [
             {
               "type": "boolean"
@@ -51034,7 +51130,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead",
+          "deprecation": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead.",
           "values": [
             {
               "type": "boolean"
@@ -51057,7 +51153,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51080,7 +51176,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51103,7 +51199,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead",
+          "deprecation": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead.",
           "values": [
             {
               "type": "boolean"
@@ -51126,7 +51222,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showMaxAllowableAssociationsSlider instead",
+          "deprecation": "since 4.32, use showMaxAllowableAssociationsSlider instead.",
           "values": [
             {
               "type": "boolean"
@@ -51149,7 +51245,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead",
+          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead.",
           "values": [
             {
               "type": "boolean"
@@ -51172,7 +51268,7 @@
           "docs": "",
           "docsTags": [],
           "default": "false",
-          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead",
+          "deprecation": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead.",
           "values": [
             {
               "type": "boolean"
@@ -51195,7 +51291,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51218,7 +51314,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead.",
           "values": [
             {
               "type": "boolean"
@@ -51241,7 +51337,7 @@
           "docs": "",
           "docsTags": [],
           "default": "true",
-          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead",
+          "deprecation": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead.",
           "values": [
             {
               "type": "boolean"
@@ -51817,6 +51913,10 @@
           "reflectToAttr": false,
           "docs": "Stores the result of completed traces.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace.html#traceResults)",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -51842,7 +51942,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Trace component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -53875,7 +53975,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Validate Topology component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -55993,7 +56093,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisVideoPlayer component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Video Player component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [],
@@ -56450,7 +56550,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Weather component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -56838,7 +56938,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Zoom component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {