- context
- isLoading
-- loader
- loadingError
- props
- refs
@@ -1092,9 +1084,6 @@ Should be used with type annotation or static contextType.
isLoading
• isLoading: boolean = false
-loader
-• loader: IReactionDisposer
-
loadingError
• loadingError: ReactNode
@@ -1264,11 +1253,10 @@ the entire component tree to unmount.
React.Component.componentDidCatch
componentDidMount
-▸ Optional componentDidMount(): void
-Called immediately after a component is mounted. Setting state here will trigger re-rendering.
+▸ componentDidMount(): void
Returns
void
-Inherited from
+Overrides
React.Component.componentDidMount
componentDidUpdate
@@ -1300,7 +1288,7 @@ the entire component tree to unmount.
Returns
void
-Inherited from
+Inherited from
React.Component.componentDidUpdate
componentWillMount
@@ -1314,7 +1302,7 @@ prevents this from being invoked.
see https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html#gradual-migration-path
Returns
void
-Inherited from
+Inherited from
React.Component.componentWillMount
componentWillReceiveProps
@@ -1349,7 +1337,7 @@ prevents this from being invoked.
Returns
void
-Inherited from
+Inherited from
React.Component.componentWillReceiveProps
componentWillUnmount
@@ -1358,7 +1346,7 @@ prevents this from being invoked.
cancelled network requests, or cleaning up any DOM elements created in componentDidMount.
Returns
void
-Inherited from
+Inherited from
React.Component.componentWillUnmount
componentWillUpdate
@@ -1395,7 +1383,7 @@ prevents this from being invoked.
Returns
void
-Inherited from
+Inherited from
React.Component.componentWillUpdate
forceUpdate
@@ -1417,7 +1405,7 @@ prevents this from being invoked.
Returns
void
-Inherited from
+Inherited from
React.Component.forceUpdate
getSnapshotBeforeUpdate
@@ -1448,14 +1436,14 @@ lifecycle events from running.
Returns
any
-Inherited from
+Inherited from
React.Component.getSnapshotBeforeUpdate
render
▸ render(): Element
Returns
Element
-Overrides
+Overrides
React.Component.render
setState
@@ -1496,7 +1484,7 @@ lifecycle events from running.
Returns
void
-Inherited from
+Inherited from
React.Component.setState
shouldComponentUpdate
@@ -1532,7 +1520,7 @@ and componentDidUpdate will not be called.
Returns
boolean
-Inherited from
+Inherited from
React.Component.shouldComponentUpdate
diff --git a/master/extensions/api/classes/Renderer.Ipc/index.html b/master/extensions/api/classes/Renderer.Ipc/index.html
index bd5be3241e..ba417892ee 100644
--- a/master/extensions/api/classes/Renderer.Ipc/index.html
+++ b/master/extensions/api/classes/Renderer.Ipc/index.html
@@ -918,7 +918,7 @@
[IpcPrefix]
• Readonly [IpcPrefix]: string
Inherited from
-IpcRegistrar.__@IpcPrefix@45768
+IpcRegistrar.__@IpcPrefix@45808
extension
• Protected extension: LensExtension
diff --git a/master/extensions/api/classes/Renderer.LensExtension/index.html b/master/extensions/api/classes/Renderer.LensExtension/index.html
index 56df8c86a1..66fcaf78b2 100644
--- a/master/extensions/api/classes/Renderer.LensExtension/index.html
+++ b/master/extensions/api/classes/Renderer.LensExtension/index.html
@@ -1181,7 +1181,7 @@
[Disposers]
• [Disposers]: ExtendableDisposer
Inherited from
-LensExtension.__@Disposers@9899
+LensExtension.__@Disposers@9904
additionalCategoryColumns
• additionalCategoryColumns: AdditionalCategoryColumnRegistration[] = []
@@ -1307,7 +1307,7 @@
Returns
void
Inherited from
-LensExtension.__@setLensExtensionDependencies@9903
+LensExtension.__@setLensExtensionDependencies@9908
activate
▸ activate(): void | Promise<void>
diff --git a/master/search/search_index.json b/master/search/search_index.json
index 80b73f54fd..dddce72ce2 100644
--- a/master/search/search_index.json
+++ b/master/search/search_index.json
@@ -1 +1 @@
-{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Lens Extension API # Customize and enhance the Lens experience with the Lens Extension API. Use the extension API to create menus or page content. The same extension API was used to create many of Lens's core features. To install your first extension you should goto the extension page in lens. This documentation describes: How to build, run, test, and publish an extension. How to take full advantage of the Lens Extension API. Where to find guides and code samples to help get you started. What Extensions Can Do # Here are some examples of what you can achieve with the Extension API: Add custom components & views in the UI - Extending the Lens Workbench For an overview of the Lens Extension API, refer to the Common Capabilities page. Extension Guides Overview also includes a list of code samples and guides that illustrate various ways of using the Lens Extension API. How to Build Extensions # Here is what each section of the Lens Extension API docs can help you with: Getting Started teaches fundamental concepts for building extensions with the Hello World sample. Extension Capabilities dissects Lens's Extension API into smaller categories and points you to more detailed topics. Extension Guides includes guides and code samples that explain specific usages of Lens Extension API. Testing and Publishing includes in-depth guides on various extension development topics, such as testing and publishing extensions. API Reference contains exhaustive references for the Lens Extension API, Contribution Points, and many other topics. What's New # Just like Lens itself, the extension API updates on a monthly cadence, rolling out new features with every release. Keep up with Lens and the Lens Extension API by reviewing the release notes . Important changes since Lens v4 # Lens has undergone major design improvements in v5, which have resulted in several large changes to the extension API. Workspaces are gone, and the catalog is introduced for containing clusters, as well as other items, including custom entities. Lens has migrated from using mobx 5 to mobx 6 for internal state management, and this may have ramifications for extension implementations. Although the API retains many components from v4, given these changes, extensions written for Lens v4 are not compatible with the Lens v5 extension API. See the Lens v4 to v5 extension migration notes on getting old extensions working in Lens v5. Looking for Help # If you have questions for extension development, try asking on the Lens Dev Slack . It's a public chatroom for Lens developers, where Lens team members chime in from time to time. To provide feedback on the documentation or issues with the Lens Extension API, create new issues at lensapp/lens . Please use the labels area/documentation and/or area/extension . Downloading Lens # Download Lens for macOS, Windows, or Linux.","title":"Overview"},{"location":"#lens-extension-api","text":"Customize and enhance the Lens experience with the Lens Extension API. Use the extension API to create menus or page content. The same extension API was used to create many of Lens's core features. To install your first extension you should goto the extension page in lens. This documentation describes: How to build, run, test, and publish an extension. How to take full advantage of the Lens Extension API. Where to find guides and code samples to help get you started.","title":"Lens Extension API"},{"location":"#what-extensions-can-do","text":"Here are some examples of what you can achieve with the Extension API: Add custom components & views in the UI - Extending the Lens Workbench For an overview of the Lens Extension API, refer to the Common Capabilities page. Extension Guides Overview also includes a list of code samples and guides that illustrate various ways of using the Lens Extension API.","title":"What Extensions Can Do"},{"location":"#how-to-build-extensions","text":"Here is what each section of the Lens Extension API docs can help you with: Getting Started teaches fundamental concepts for building extensions with the Hello World sample. Extension Capabilities dissects Lens's Extension API into smaller categories and points you to more detailed topics. Extension Guides includes guides and code samples that explain specific usages of Lens Extension API. Testing and Publishing includes in-depth guides on various extension development topics, such as testing and publishing extensions. API Reference contains exhaustive references for the Lens Extension API, Contribution Points, and many other topics.","title":"How to Build Extensions"},{"location":"#whats-new","text":"Just like Lens itself, the extension API updates on a monthly cadence, rolling out new features with every release. Keep up with Lens and the Lens Extension API by reviewing the release notes .","title":"What's New"},{"location":"#important-changes-since-lens-v4","text":"Lens has undergone major design improvements in v5, which have resulted in several large changes to the extension API. Workspaces are gone, and the catalog is introduced for containing clusters, as well as other items, including custom entities. Lens has migrated from using mobx 5 to mobx 6 for internal state management, and this may have ramifications for extension implementations. Although the API retains many components from v4, given these changes, extensions written for Lens v4 are not compatible with the Lens v5 extension API. See the Lens v4 to v5 extension migration notes on getting old extensions working in Lens v5.","title":"Important changes since Lens v4"},{"location":"#looking-for-help","text":"If you have questions for extension development, try asking on the Lens Dev Slack . It's a public chatroom for Lens developers, where Lens team members chime in from time to time. To provide feedback on the documentation or issues with the Lens Extension API, create new issues at lensapp/lens . Please use the labels area/documentation and/or area/extension .","title":"Looking for Help"},{"location":"#downloading-lens","text":"Download Lens for macOS, Windows, or Linux.","title":"Downloading Lens"},{"location":"extensions/extension-migration/","text":"Lens v4 to v5 Extension Migration Notes # Lens v5 inspects the version of the extension to ensure it is compatible. The package.json for your extension must have an \"engines\" field specifying the lens version that your extension is targeted for, e.g: \"engines\": { \"lens\": \"^5.0.0-beta.7\" }, Note that Lens v5 supports all the range semantics that semver provides. Types and components have been reorganized, many have been grouped by process ( Main and Renderer ) plus those not specific to a process ( Common ). For example the LensMainExtension class is now referred to by Main.LensExtension . See the API Reference for the new organization. The globalPageMenus field of the Renderer extension class (now Renderer.LensExtension ) is removed. Global pages can still be made accessible via the application menus and the status bar, as well as from the newly added Welcome menu. The clusterFeatures field of the Renderer extension class (now Renderer.LensExtension ) is removed. Cluster features can still be implemented but Lens no longer dictates how a feature's lifecycle (install/upgrade/uninstall) is managed. Renderer.K8sApi.ResourceStack provides the functionality to input and apply kubernetes resources to a cluster. It is up to the extension developer to manage the lifecycle. It could be applied automatically to a cluster by the extension or the end-user could be expected to install it, etc. from the cluster Settings page. Lens v5 now relies on mobx 6 for state management. Extensions that use mobx will need to be modified to work with mobx 6. See Migrating from Mobx 4/5 for specific details. For an example of an existing extension that is compatible with Lens v5 see the Lens Resource Map Extension","title":"Lens v4 to v5 Extension Migration Notes"},{"location":"extensions/extension-migration/#lens-v4-to-v5-extension-migration-notes","text":"Lens v5 inspects the version of the extension to ensure it is compatible. The package.json for your extension must have an \"engines\" field specifying the lens version that your extension is targeted for, e.g: \"engines\": { \"lens\": \"^5.0.0-beta.7\" }, Note that Lens v5 supports all the range semantics that semver provides. Types and components have been reorganized, many have been grouped by process ( Main and Renderer ) plus those not specific to a process ( Common ). For example the LensMainExtension class is now referred to by Main.LensExtension . See the API Reference for the new organization. The globalPageMenus field of the Renderer extension class (now Renderer.LensExtension ) is removed. Global pages can still be made accessible via the application menus and the status bar, as well as from the newly added Welcome menu. The clusterFeatures field of the Renderer extension class (now Renderer.LensExtension ) is removed. Cluster features can still be implemented but Lens no longer dictates how a feature's lifecycle (install/upgrade/uninstall) is managed. Renderer.K8sApi.ResourceStack provides the functionality to input and apply kubernetes resources to a cluster. It is up to the extension developer to manage the lifecycle. It could be applied automatically to a cluster by the extension or the end-user could be expected to install it, etc. from the cluster Settings page. Lens v5 now relies on mobx 6 for state management. Extensions that use mobx will need to be modified to work with mobx 6. See Migrating from Mobx 4/5 for specific details. For an example of an existing extension that is compatible with Lens v5 see the Lens Resource Map Extension","title":"Lens v4 to v5 Extension Migration Notes"},{"location":"extensions/api/","text":"Extension API Reference # APIs # Common Main Renderer","title":"API Reference"},{"location":"extensions/api/#extension-api-reference","text":"","title":"Extension API Reference"},{"location":"extensions/api/#apis","text":"Common Main Renderer","title":"APIs"},{"location":"extensions/api/modules/","text":"@k8slens/extensions # Table of contents # Namespaces # Common Main Renderer","title":"@k8slens/extensions"},{"location":"extensions/api/modules/#k8slensextensions","text":"","title":"@k8slens/extensions"},{"location":"extensions/api/modules/#table-of-contents","text":"","title":"Table of contents"},{"location":"extensions/api/modules/#namespaces","text":"Common Main Renderer","title":"Namespaces"},{"location":"extensions/api/classes/Common.Catalog.CatalogCategory/","text":"Class: CatalogCategory # Common . Catalog .CatalogCategory Hierarchy # TypedEventEmitter < CatalogCategoryEvents , this > \u21b3 CatalogCategory Table of contents # Constructors # constructor Properties # apiVersion filters kind metadata spec Methods # addListener addMenuFilter emit eventNames filteredItems getId getMaxListeners listenerCount listeners off on once prependListener prependOnceListener rawListeners removeAllListeners removeListener setMaxListeners parseId Constructors # constructor # \u2022 new CatalogCategory () Inherited from # (EventEmitter as new () => TypedEmitter).constructor Properties # apiVersion # \u2022 Readonly Abstract apiVersion : string The version of category that you are wanting to declare. Currently supported values: \"catalog.k8slens.dev/v1alpha1\" filters # \u2022 Protected filters : ObservableSet < AddMenuFilter > internal kind # \u2022 Readonly Abstract kind : string The kind of item you wish to declare. Currently supported values: \"CatalogCategory\" metadata # \u2022 Readonly Abstract metadata : Object The data about the category itself Type declaration # Name Type Description icon string Either an