-
Notifications
You must be signed in to change notification settings - Fork 615
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
ODC-7720: Add dev perspective nav options to admin perspective #14588
base: master
Are you sure you want to change the base?
Conversation
@vikram-raj: This pull request references ODC-7720 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vikram-raj 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:
Approvers can indicate their approval by writing |
"href": "/topology", | ||
"namespaced": true, | ||
"dataAttributes": { | ||
"data-quickstart-id": "qs-nav-topology", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me realize that we should look at the quick starts to see what changes are needed for the combined perspective. We should track that as a story under the convergence epic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure I will create a story for a quick start under epic ODC-7716
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @vikram-raj 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this isn't a lot of code, is there a reason we can't reuse the dev console list page here and for helm repositories? Are there not corresponding pages on the dev side?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a list page for this and using the same, I need to create this component as in dev perspective Helm page is tabbed view and the list page component does not contain a title, create button and Namespace selector.
|
||
const PageContents: React.FC<PageContentsProps> = ({ namespace }) => { | ||
const { t } = useTranslation(); | ||
return namespace ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should support showing releases in all namespaces (for users with authority) rather than falling back to the project list in the admin/converged perspective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, I will update it. As an Admin perspective do support All namespaces.
|
||
const PageContents: React.FC<PageContentsProps> = ({ namespace }) => { | ||
const { t } = useTranslation(); | ||
return namespace ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support an all namespaces list?
"id": "software-catalog", | ||
"perspective": "admin", | ||
"section": "home", | ||
"name": "%devconsole~Software Catalog%", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I worry that this will be confused with OperatorHub, although I know this is in @kevinhatchoua's mock. This is the +Add
page on the dev side, correct? I also worry that we'll have different labels in the admin and dev perspectives when they're both enabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it is not a +Add
page. It is a Catalog page showing all the catalogs of 'Builder Images,
DevFiles,
Templates,
Event Sources`, etc. We should have the same labels in both perspectives, as there is no difference in content. Software Catalog in Admin and Developer Catalog in the Dev perspective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On creating of serverless function, user is redirected to workloads tab in Project details page.
Screen.Recording.2024-12-09.at.1.53.51.PM.mov
It was an expected behavior as that's a topology page in the admin perspective. But now we have a Topology page in admin perspective we should redirect the user to that page. I will update it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I am in Helm release or repositories page and onClick of Helm release or repository, select item in the left navigation menu is not proper.
Screen.Recording.2024-12-10.at.11.49.22.AM.mov
Developer catalog is replaced as Software catalog in navigation menu and page title but if I select a catalog type, breadcrumbs is still mentioned as developer catalog and in the highlighted description also. is this fine? or else can we keep in all the places as either Software catalog or Developer catalog?
Screen.Recording.2024-12-10.at.11.53.42.AM.mov
@vikram-raj: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For Helm repository details page, if it is Helm chart repository, breadcrumbs is redirecting to Helm Chart Repositories list page and if it is PHCR, breadcrumbs is redirecting to Project Helm Chart Repositories list page unlike the behaviour in existing design where breadcrumbs redirecting to Repositories list page irrespective of whether it is HCR or PHCR.
----New design---
Screen.Recording.2024-12-11.at.11.41.26.AM.mov
---Old design----
Screen.Recording.2024-12-11.at.11.46.03.AM.mov
@lokanandaprabhu I have fixed the breadcrumb link in the dev perspective. And I asked UX whether we can expose the HCR and PHCR directly as nav items instead of combining both in the single list page. |
Story: https://issues.redhat.com/browse/ODC-7720
Descriptions:
Software Catalog
nav option under theHome
section in the Admin perspectiveHelm
nav option belowOperators
option in the Admin perspectiveFunctions
nav option under theServerless
section in the Admin perspectiveODC-7720.mov