-
Notifications
You must be signed in to change notification settings - Fork 670
Show full CSV description as markdown in dev catalog item details #3734
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
Show full CSV description as markdown in dev catalog item details #3734
Conversation
|
fyi @sspeiche @openshift/team-devconsole-ux |
|
@rohitkrai03 can we possibly change the format? Description Operator Description |
|
fyi @dmesser |
3d968f7 to
2bf44dc
Compare
2bf44dc to
f60a8d0
Compare
@serenamarie125 Updated as per your suggestion. This is how it looks like now - |
|
@rohitkrai03 I think there's a hierarchy issue because the operator name is larger than the description titles. Can you please make Description & Operator Description h1s? |
|
@itsptk do you think you'd make the same change there ? |
|
My initial take is that this particular Knative Serving operator just happens to use h1 styling for that "Knative Serving" text but several other operators I checked mostly used h2 or smaller. My inclination would be to not update our existing styling to accommodate this particular operator's description hierarchy. |
|
The other thing we could do is to stylizes our markdown in this area so that h1's are the same as h2's ? |
I spoke with @maryshak1996 about this idea and I think we would go this direction in the admin console instead of making the Description headers h1s, as that would better fit the hierarchy in the installed operator details. |
|
/test e2e-gcp-console |
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.
nit: type for desc would be good to have
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.
Actually description is being reduced using multiple resources so its hard to define a strict type for it and out of scope for this story. But I have refactored the function to get more specific params with strict types.
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.
is there a possibility when desc.csv.spec.description would get undefined
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.
Don't think so. The CSV data should contain a description.
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.
Just an FYI, we did upgrade TypeScript to 3.7 and there is something called Optional Chaining now https://devblogs.microsoft.com/typescript/announcing-typescript-3-7/#optional-chaining - so checking for missing items is less of a concern.
f60a8d0 to
91d029c
Compare
|
/lgtm |
|
/lgtm cancel |
|
/lgtm |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
20 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/hold |
|
/kind feature |
|
/hold cancel |


Related Story - https://jira.coreos.com/browse/ODC-2457
This PR -
Screenshots -
Before -

After -
