Navigation refactoring, handling extension page params

[ixrock]

• Custom page params
• Detached bunch of unrelated url-params from renderer/navigation.ts with new helper Navigation.createPageParam({name: string, defaultValue?: any, parse?(), stringify?(), ...})
• Simplified page-registry, so it doesn't need to care about dynamic params part of final page URL
• [BREAKING]: pageInit.id stops supporting dynamic param placeholders, e.g. /users/:user
• [BREAKING]: pageInit.exact option removed

close #1399

Example from extensions/example-extension/renderer.tsx:

export default class ExampleExtension extends LensRendererExtension {
  clusterPages: Interface.PageRegistration[] = [
    {
      components: {
        Page: (props: Interface.PageComponentProps<ExamplePageParams>) => {
          return <ExamplePage {...props} extension={this}/>;
        },
      },
      params: {
        // setup basic param "exampleId" with default value "demo"
        exampleId: "demo",

        // setup advanced multi-values param "selectedNamespaces" with custom parsing/stringification
        selectedNamespaces: {
          defaultValueStringified: ["default", "kube-system"],
          multiValues: true,
          parse(values: string[]) { // from URL
            return values.map(name => namespaceStore.getByName(name)).filter(Boolean);
          },
          stringify(values: K8sApi.Namespace[]) { // to URL
            return values.map(namespace => namespace.getName());
          },
        }
      }
    }
  ];

  clusterPageMenus: Interface.PageMenuRegistration[] = [
    {
      title: "Example extension",
      components: {
        Icon: ExampleIcon,
      },
    },
  ];
}

[Nokel81]

I have reviews some of these changes. I will continue the review tomorrow. But there are some things already that need to be changed.

[ixrock]

Besides all technical details and breaking changes.. what do you think about the concept?

[stefcameron]

This is a good change, but I think the interface could be improved a bit.

[jim-docker]

I think this PR breaks the foldout menu feature (using id/parentId fields of the ClusterPageMenuRegistration interface). I have examples that work in master but not in this branch.

[ixrock]

I think this PR breaks the foldout menu feature (using id/parentId fields of the ClusterPageMenuRegistration interface). I have examples that work in master but not in this branch.

@jim-docker could you please check this one more time? I've merged master and reverted most of the part for sidebar menu logic, so would possibly work now.

[jim-docker]

I think this PR breaks the foldout menu feature (using id/parentId fields of the ClusterPageMenuRegistration interface). I have examples that work in master but not in this branch.

@jim-docker could you please check this one more time? I've merged master and reverted most of the part for sidebar menu logic, so would possibly work now.

Yes, works again 👍