Describe the bugClusterPageMenus have a hierarchy of parent menus by way of id and parentId matching. However, if a child of a root menu item doesn't have a target then it is not shown. Furthermore, of a child of a root menu has itself a child, that grandchild of a root menu is never rendered
Expected behaviorClusterPageMenu's should always be rendered, even if they don't have a matching entry and they should do somethings sane if clicked (maybe a warning notification)
Furthermore, menus should be able to be arbitrarily nested.
Initially the docs should be modified to specify that this is only supported to a single level of nesting, before the work to support N levels is done.
Describe the bug
ClusterPageMenus
have a hierarchy of parent menus by way ofid
andparentId
matching. However, if a child of a root menu item doesn't have a target then it is not shown. Furthermore, of a child of a root menu has itself a child, that grandchild of a root menu is never renderedTo Reproduce Steps to reproduce the behaviour:
Example Extension
```ts export default class ThingExtension extends LensRendererExtension { clusterPages = [ { id: "thing_page_1", components: { Page: (): JSX.Element => (page 1
) } }, { id: "thing_page_2", components: { Page: (): JSX.Element => (page 2
) } }, { id: "thing_page_3a", components: { Page: (): JSX.Element => (page 3a
) } }, ] clusterPageMenus = [ { id: "thing", title: "thing", components: { Icon: MyIcon } }, { parentId: "thing", target: { pageId: "thing_page_1", params: {} }, title: "1", components: { Icon: (): JSX.Element =>Observe that only the following is rendered:
Expected behavior
ClusterPageMenu
's should always be rendered, even if they don't have a matching entry and they should do somethings sane if clicked (maybe a warning notification)Furthermore, menus should be able to be arbitrarily nested.