@arcgis/map-components 5.0.0-next.23 → 5.0.0-next.25

package/dist/docs/api.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-10-16T04:40:24",
+  "timestamp": "2025-10-18T04:40:37",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "5.0.0-next.23",
+    "version": "5.0.0-next.25",
     "typescriptVersion": "5.8.3"
   },
   "schemaVersion": "1.0.0",
@@ -427,7 +427,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -1094,7 +1094,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Area Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -2530,7 +2530,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Gallery component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -3536,7 +3536,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -4459,7 +4459,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Basemap Toggle component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -4810,7 +4810,7 @@
             {
               "kind": "field",
               "name": "defaultCreateOptions",
-              "description": "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.",
+              "description": "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.",
               "type": {
                 "text": "BookmarkOptions",
                 "references": [
@@ -4834,7 +4834,7 @@
             {
               "kind": "field",
               "name": "defaultEditOptions",
-              "description": "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.",
+              "description": "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.",
               "type": {
                 "text": "BookmarkOptions",
                 "references": [
@@ -4984,6 +4984,12 @@
                   ]
                 }
               },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "signature": "(bookmark: __esri.Bookmark): Promise<void>"
             },
             {
@@ -5034,6 +5040,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```"
@@ -5144,7 +5154,13 @@
               "description": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
               "type": {
                 "text": "Record<string, unknown>"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -5419,7 +5435,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Bookmarks component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -5820,7 +5836,7 @@
           "events": [
             {
               "name": "arcgisBookmarkEdit",
-              "description": "\nFires when a [Bookmark](https://developers.arcgis.com/javascript/latest/api-reference/esri-webmap-Bookmark.html) is edited.",
+              "description": "Fires when a [Bookmark](https://developers.arcgis.com/javascript/latest/api-reference/esri-webmap-Bookmark.html) is edited.",
               "type": {
                 "text": "BookmarksBookmarkEditEvent",
                 "references": [
@@ -5834,6 +5850,10 @@
                 ]
               },
               "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```"
@@ -5856,6 +5876,10 @@
                 ]
               },
               "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```"
@@ -6288,7 +6312,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Building Explorer component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -7106,7 +7130,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Catalog Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -7903,7 +7927,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Compass component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -8916,7 +8940,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Coordinate Conversion component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -9817,20 +9841,6 @@
                 }
               ]
             },
-            {
-              "kind": "field",
-              "name": "supported",
-              "type": {
-                "text": "boolean",
-                "values": [
-                  {
-                    "type": "boolean"
-                  }
-                ]
-              },
-              "default": "false",
-              "readonly": true
-            },
             {
               "kind": "field",
               "name": "timeSliderPosition",
@@ -10678,7 +10688,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directional Pad component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -11581,7 +11591,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Directions component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -12373,7 +12383,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Direct Line Measurement 3D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -13016,7 +13026,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Distance Measurement 2D component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -14065,7 +14075,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Editor component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -14445,7 +14455,13 @@
                     "end": 23
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisSketchUpdate",
@@ -14461,7 +14477,13 @@
                     "end": 23
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             }
           ]
         }
@@ -15135,7 +15157,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -16335,7 +16357,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Elevation Profile Next component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -17190,7 +17212,13 @@
               "description": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
               "type": {
                 "text": "Record<string, unknown>"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -17431,12 +17459,18 @@
               "readonly": true,
               "attribute": "state",
               "reflects": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "docsOnlyReadonly": true
             },
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Expand component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -18140,7 +18174,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-attachments-content"
+              "attribute": "hide-attachments-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18277,7 +18317,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-expression-content"
+              "attribute": "hide-expression-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18292,7 +18338,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-fields-content"
+              "attribute": "hide-fields-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18359,7 +18411,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-media-content"
+              "attribute": "hide-media-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18374,7 +18432,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-text-content"
+              "attribute": "hide-text-content",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -18507,7 +18571,7 @@
             {
               "kind": "field",
               "name": "messageOverrides",
-              "description": "Overwrite localized strings for this component.",
+              "description": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
               "type": {
                 "text": "Record<string, unknown>"
               },
@@ -18880,7 +18944,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -18926,7 +18990,13 @@
                     "end": 16
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             }
           ],
           "attributes": [
@@ -22719,7 +22789,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Feature Table component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -24686,7 +24756,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "default-popup-template-enabled"
+              "attribute": "default-popup-template-enabled",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "method",
@@ -24764,7 +24840,13 @@
                   }
                 ]
               },
-              "attribute": "feature-menu-title"
+              "attribute": "feature-menu-title",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25019,6 +25101,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```"
@@ -25104,7 +25190,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "hide-feature-list-layer-title"
+              "attribute": "hide-feature-list-layer-title",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25235,7 +25327,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "include-default-actions-disabled"
+              "attribute": "include-default-actions-disabled",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25313,7 +25411,13 @@
               "description": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
               "type": {
                 "text": "Record<string, unknown>"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "method",
@@ -25685,6 +25789,12 @@
                   ]
                 }
               },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "signature": "(): Promise<void>",
               "async": true
             },
@@ -25882,7 +25992,13 @@
                     "end": 17
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -25897,7 +26013,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "visible"
+              "attribute": "visible",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             }
           ],
           "attributes": [
@@ -26826,7 +26948,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Floor Filter component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -28219,7 +28341,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Grid Controls component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -29948,7 +30070,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Home component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -30970,7 +31092,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Layer List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -31490,7 +31612,7 @@
           "customElement": true,
           "name": "ArcgisLegend",
           "tagName": "arcgis-legend",
-          "description": "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.",
+          "description": "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.",
           "demos": [
             {
               "description": "Docs",
@@ -31909,10 +32031,16 @@
             {
               "kind": "field",
               "name": "messageOverrides",
-              "description": "Overwrite localized strings for this component",
+              "description": "Replace localized message strings with your own strings.\n\n_**Note**: Individual message keys may change between releases._",
               "type": {
                 "text": "Record<string, unknown>"
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -32094,7 +32222,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Legend component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -32815,7 +32943,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Line Of Sight component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -33202,7 +33330,13 @@
                     "end": 19
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -34481,6 +34615,12 @@
                   ]
                 }
               },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "signature": "(analysis: __esri.Analysis): Promise<__esri.AnalysisView2DUnion>",
               "async": true
             },
@@ -34794,7 +34934,13 @@
                     "end": 27
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewAnalysisViewCreateError",
@@ -34810,7 +34956,13 @@
                     "end": 32
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewAnalysisViewDestroy",
@@ -34826,7 +34978,13 @@
                     "end": 28
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewChange",
@@ -35663,7 +35821,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Link Chart Layout Switcher component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView",
                 "references": [
@@ -36315,7 +36473,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Locate component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -36875,7 +37033,13 @@
                     "end": 19
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -38490,6 +38654,12 @@
                   ]
                 }
               },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ],
               "signature": "(analysis: __esri.Analysis): Promise<__esri.AnalysisView2DUnion>",
               "async": true
             },
@@ -38830,7 +39000,13 @@
                     "end": 27
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewAnalysisViewCreateError",
@@ -38846,7 +39022,13 @@
                     "end": 32
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewAnalysisViewDestroy",
@@ -38862,7 +39044,13 @@
                     "end": 28
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "name": "arcgisViewChange",
@@ -39826,7 +40014,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Measurement component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -40466,7 +40654,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Navigation Toggle component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -41108,7 +41296,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Oriented Imagery Viewer component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -41590,7 +41778,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Placement component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -43074,7 +43262,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPopup component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Popup component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -44241,7 +44429,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Print component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -44895,7 +45083,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Bar component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -45514,7 +45702,13 @@
                 ]
               },
               "default": "false",
-              "attribute": "show-world-value"
+              "attribute": "show-world-value",
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -45542,7 +45736,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Scale Range Slider component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -49665,7 +49859,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Search component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -50968,7 +51162,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Shadow Cast component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -52570,7 +52764,7 @@
             {
               "kind": "field",
               "name": "toolbarKind",
-              "description": "Controls the appearance of the sketch widget, allowing\nthe toolbar to adapt its appearance appropriately based on context.",
+              "description": "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.",
               "type": {
                 "text": "\"docked\" | \"floating\"",
                 "values": [
@@ -52741,7 +52935,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Sketch component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -53311,7 +53505,7 @@
             },
             {
               "name": "toolbar-kind",
-              "description": "Controls the appearance of the sketch widget, allowing\nthe toolbar to adapt its appearance appropriately based on context.",
+              "description": "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.",
               "type": {
                 "text": "\"docked\" | \"floating\"",
                 "values": [
@@ -53898,7 +54092,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Slice component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -54544,7 +54738,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Swipe component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -55112,7 +55306,13 @@
                     "type": "WebMap"
                   }
                 ]
-              }
+              },
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
@@ -55438,7 +55638,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Table List component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "LinkChartView | MapView | SceneView",
                 "references": [
@@ -56592,7 +56792,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Time Slider component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -57048,6 +57248,10 @@
               "attribute": "icon",
               "reflects": true,
               "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                },
                 {
                   "name": "see",
                   "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
@@ -57864,7 +58068,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Track component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [
@@ -58294,6 +58498,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsColorPicker",
+              "description": "If true, hides the connectivity association color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58308,6 +58513,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsStylePicker",
+              "description": "If true, hides the connectivity association style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58322,6 +58528,7 @@
             {
               "kind": "field",
               "name": "hideConnectivityAssociationsSettingsWidthInput",
+              "description": "If true, hides the connectivity association width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58336,6 +58543,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsColorPicker",
+              "description": "If true, hides the structural attachment associations color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58350,6 +58558,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsStylePicker",
+              "description": "If true, hides the structural attachment associations style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58364,6 +58573,7 @@
             {
               "kind": "field",
               "name": "hideStructuralAttachmentAssociationsSettingsWidthInput",
+              "description": "If true, hides the structural attachment associations width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58644,6 +58854,7 @@
             {
               "kind": "field",
               "name": "showConnectivityAssociationsSettingsArrowsToggle",
+              "description": "If true, shows the connectivity association arrows toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58658,6 +58869,7 @@
             {
               "kind": "field",
               "name": "showConnectivityAssociationsSettingsCapSelect",
+              "description": "If true, shows the connectivity association cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58672,6 +58884,7 @@
             {
               "kind": "field",
               "name": "showMaxAllowableAssociationsSlider",
+              "description": "If true, hides the max allowable associations slider.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58686,6 +58899,7 @@
             {
               "kind": "field",
               "name": "showStructuralAttachmentAssociationsSettingsArrowsToggle",
+              "description": "If true, shows the structural attachment associations arrow toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58700,6 +58914,7 @@
             {
               "kind": "field",
               "name": "showStructuralAttachmentAssociationsSettingsCapSelect",
+              "description": "If true, shows the structural attachment associations cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58750,7 +58965,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Associations component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -58777,7 +58992,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead",
+              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead.",
               "attribute": "visible-elements-connectivity-associations-settings-arrows-toggle"
             },
             {
@@ -58792,7 +59007,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead",
+              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead.",
               "attribute": "visible-elements-connectivity-associations-settings-cap-select"
             },
             {
@@ -58807,7 +59022,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead.",
               "attribute": "visible-elements-connectivity-associations-settings-color-picker"
             },
             {
@@ -58822,7 +59037,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead.",
               "attribute": "visible-elements-connectivity-associations-settings-style-picker"
             },
             {
@@ -58837,7 +59052,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead",
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead.",
               "attribute": "visible-elements-connectivity-associations-settings-width-input"
             },
             {
@@ -58852,7 +59067,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead",
+              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead.",
               "attribute": "visible-elements-max-allowable-associations-slider"
             },
             {
@@ -58867,7 +59082,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead",
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-arrows-toggle"
             },
             {
@@ -58882,7 +59097,7 @@
                 ]
               },
               "default": "false",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead",
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-cap-select"
             },
             {
@@ -58897,7 +59112,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-color-picker"
             },
             {
@@ -58912,7 +59127,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-style-picker"
             },
             {
@@ -58927,7 +59142,7 @@
                 ]
               },
               "default": "true",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead",
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead.",
               "attribute": "visible-elements-structural-attachment-associations-settings-width-input"
             }
           ],
@@ -58962,6 +59177,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-color-picker",
+              "description": "If true, hides the connectivity association color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58975,6 +59191,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-style-picker",
+              "description": "If true, hides the connectivity association style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -58988,6 +59205,7 @@
             },
             {
               "name": "hide-connectivity-associations-settings-width-input",
+              "description": "If true, hides the connectivity association width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59001,6 +59219,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-color-picker",
+              "description": "If true, hides the structural attachment associations color picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59014,6 +59233,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-style-picker",
+              "description": "If true, hides the structural attachment associations style picker.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59027,6 +59247,7 @@
             },
             {
               "name": "hide-structural-attachment-associations-settings-width-input",
+              "description": "If true, hides the structural attachment associations width input.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59249,6 +59470,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-arrows-toggle",
+              "description": "If true, shows the connectivity association arrows toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59262,6 +59484,7 @@
             },
             {
               "name": "show-connectivity-associations-settings-cap-select",
+              "description": "If true, shows the connectivity association cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59275,6 +59498,7 @@
             },
             {
               "name": "show-max-allowable-associations-slider",
+              "description": "If true, hides the max allowable associations slider.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59288,6 +59512,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-arrows-toggle",
+              "description": "If true, shows the structural attachment associations arrow toggle.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59301,6 +59526,7 @@
             },
             {
               "name": "show-structural-attachment-associations-settings-cap-select",
+              "description": "If true, shows the structural attachment associations cap select.",
               "type": {
                 "text": "boolean",
                 "values": [
@@ -59324,7 +59550,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsArrowsToggle",
-              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead"
+              "deprecated": "since 4.32, showConnectivityAssociationsSettingsArrowsToggle instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-cap-select",
@@ -59338,7 +59564,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsCapSelect",
-              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead"
+              "deprecated": "since 4.32, use showConnectivityAssociationsSettingsCapSelect instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-color-picker",
@@ -59352,7 +59578,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsColorPicker",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsColorPicker instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-style-picker",
@@ -59366,7 +59592,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsStylePicker",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsStylePicker instead."
             },
             {
               "name": "visible-elements-connectivity-associations-settings-width-input",
@@ -59380,7 +59606,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsConnectivityAssociationsSettingsWidthInput",
-              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead"
+              "deprecated": "since 4.32, use hideConnectivityAssociationsSettingsWidthInput instead."
             },
             {
               "name": "visible-elements-max-allowable-associations-slider",
@@ -59394,7 +59620,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsMaxAllowableAssociationsSlider",
-              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead"
+              "deprecated": "since 4.32, use showMaxAllowableAssociationsSlider instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-arrows-toggle",
@@ -59408,7 +59634,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsArrowsToggle",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead"
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsArrowsToggle instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-cap-select",
@@ -59422,7 +59648,7 @@
               },
               "default": "false",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsCapSelect",
-              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead"
+              "deprecated": "since 4.32, use showStructuralAttachmentAssociationsSettingsCapSelect instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-color-picker",
@@ -59436,7 +59662,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsColorPicker",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsColorPicker instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-style-picker",
@@ -59450,7 +59676,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsStylePicker",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsStylePicker instead."
             },
             {
               "name": "visible-elements-structural-attachment-associations-settings-width-input",
@@ -59464,7 +59690,7 @@
               },
               "default": "true",
               "fieldName": "visibleElementsStructuralAttachmentAssociationsSettingsWidthInput",
-              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead"
+              "deprecated": "since 4.32, use hideStructuralAttachmentAssociationsSettingsWidthInput instead."
             }
           ],
           "events": [
@@ -59994,12 +60220,18 @@
                   }
                 ]
               },
-              "readonly": true
+              "readonly": true,
+              "docsTags": [
+                {
+                  "name": "since",
+                  "text": "4.34"
+                }
+              ]
             },
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Trace component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -62081,7 +62313,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Utility Network Validate Topology component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -64494,7 +64726,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisVideoPlayer component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Video Player component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView",
                 "references": [
@@ -65066,7 +65298,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Weather component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "SceneView",
                 "references": [
@@ -65572,7 +65804,7 @@
             {
               "kind": "field",
               "name": "view",
-              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
+              "description": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the Zoom component will be associated with a map or scene component rather than using the `view` property.",
               "type": {
                 "text": "MapView | SceneView",
                 "references": [