chore(ws): restructure frontend and setup navigation

[Griffin-Sullivan]

Restructuring the frontend to have the right directory layout. I also updated some things like README, package.json, tsconfig, webpack config, and added routes / navigation.

Most of this reflects how model registry is set up.

[ederign]

@Griffin-Sullivan overall looks good.

Do you mind to run npm audit fix in your PR? I got here and automatically fixed all vulnerabilities.

https://gist.github.com/ederign/6736f23cf5814328e92e07a8a95711b8

[ederign]

/lgtm thank you so much Griffin! Let's move forward and work on the next PR

[ederign]

/lgtm

[thesuperzapper]

@Griffin-Sullivan @ederign I think something about what you changed requires the frontend test GitHub workflow to be updated:

• https://github.com/kubeflow/notebooks/blob/notebooks-v2/.github/workflows/ui-frontend-build.yml

It's probably best if we try and get it to pass before merging, unless you have already started another PR based on this one.

[Griffin-Sullivan]

Do I need to become a member of Kubeflow for the workflow to run without approval?

[thesuperzapper]

Do I need to become a member of Kubeflow for the workflow to run without approval?

@Griffin-Sullivan, no once you get your first PR merged on the repo it will be fine.

I just approved it for now.

[Griffin-Sullivan]

apparently no tests == fail..... I'll add back the Jest test I removed and then re-remove when I add Cypress in the next PR.

[Griffin-Sullivan]

Ok so instead I actually removed the test run step from the GitHub Action since the test is out of date and there's no point to add tests right now when we will start that in the next PR.

[thesuperzapper]

@Griffin-Sullivan it looks like the CI is still failing, cant you just add a nothing test, and ensure that all the other steps in the GitHub workflow succeed?

That will make it easier when we add new tests.

[Griffin-Sullivan]

I could but I see that as pointless work when I could just fix the github action. Looks like I accidentally removed an npm command that should've stayed.

[Griffin-Sullivan]

Ok fairly confident in this one 😆

[thesuperzapper]

@Griffin-Sullivan we can merge this for now, but please remember to re-add the test call in the github action in your next PR, otherwise we will probably forget.

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ederign, thesuperzapper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thesuperzapper]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment