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
[UI] Make UI/UX consistent for Publishing catalog content. #7379
Comments
This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests Using Cypress.
|
I am willing to work on this issue! |
Can I work on this? |
Hey @Revolyssup, with respect to the following point
this is the file where I should be making changes right? if res.StatusCode != 200 {
// failsafe for the case when a valid uuid v4 is not an id of any pattern (bad api call)
return errors.Errorf("Response Status Code %d, possible invalid ID", res.StatusCode) meshery/mesheryctl/internal/cli/root/pattern/view.go if not, a little guidance on how to proceed with it will be helpful.
|
Nope, this is mesheryctl. The change would be in Meshery cloud as well as Meshery server code. I will do that. Create another issue and assign it to me. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@thisiskaransgit what's the status on this issue? // @harkiratsm |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
Current Behavior
A publish button is available currently that sends a publish request for publishing content. But there are a lot of UI/UX inconsistencies
Desired Behavior
visibility
field set toPublic
Private
andPublished
Public
andPublished
are shown asPublic
, which shouldn't be the case.a. For
public
/private
designs, have apublish
button.b. For
public
/private
designs which already have been requested to get published will result in an error. Handle the error gracefully with an error message describing that the request has been submitted and will be approved. And to prompt users to check their mail.c. For the already Published content, add an
unpublish
button for the owners and admins of the content to unpublish the catalog item.Accepted
when a publish request is submitted.Implementation
Acceptance Tests
Mockups
Contributor Guides and Handbook
The text was updated successfully, but these errors were encountered: