Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension settings side menu configuration is not honored #13396

Open
cnotv opened this issue Feb 13, 2025 · 1 comment
Open

Extension settings side menu configuration is not honored #13396

cnotv opened this issue Feb 13, 2025 · 1 comment
Assignees
Labels
area/extensions kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@cnotv
Copy link
Member

cnotv commented Feb 13, 2025

Description

Given a custom page configuration to be added in Settings is not showing in the side menu.

// Product configuration
export function init($plugin: IPlugin, store: any) {
  const {
    virtualType,
    basicType
  } = $plugin.DSL(store, PRODUCT_NAME);

  virtualType({
    label: SETTING_PAGE_NAME,
    name:  CUSTOM_PAGE_NAME,
    route: {
      name:   SETTING_PAGE_NAME,
      params: {
        product: SETTING_PRODUCT,
      }
    }
  });

  basicType([CUSTOM_PAGE_NAME]);
}
// Router configuration
const routes: RouteRecordRaw[] = [
  {
    name:      SETTING_PAGE_NAME,
    path:      `/c/:cluster/settings/${ CUSTOM_PAGE_NAME }`,
    component: Registration,
    meta:      { product: SETTING_PRODUCT },
  },
];
@cnotv cnotv added this to the v2.11.1 milestone Feb 13, 2025
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Feb 13, 2025
@richard-cox
Copy link
Member

looks like there's some misalignment between the virtualType name (should be similar to the route's url) and params (to include the PRODUCT_NAME). more info at https://extensions.rancher.io/extensions/next/api/nav/custom-page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

3 participants