Skip to content

Move to generic list and details routes #2792

Open
@sniok

Description

@sniok

Instead of defining route for each resource, we should have two routes, one for list and another for details

[
  { path: '/c/:cluster/details/:apiName/:namespace?/:name', component: KubeObjectDetails },
  { path: '/c/:cluster/details/:apiName', component: KubeObjectList }
]

This will really simplify our routing setup and also allow for easier handling of custom resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfrontendIssues related to the frontend

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions