Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create meaningful error messages by encapsulating backend server errors for Ratify Users #1681

Open
yizha1 opened this issue Aug 2, 2024 · 0 comments
Open

Create meaningful error messages by encapsulating backend server errors for Ratify Users #1681

yizha1 opened this issue Aug 2, 2024 · 0 comments

Comments

@yizha1
Copy link
Collaborator

yizha1 commented Aug 2, 2024 •
edited
Loading

This issue was created to track the following comment:

          Passing through errors is not a user-friendly practice. We need to catch the error from ACR and wrap it into something meaningful\ for the user of Rarify. The user of Ratify may have no knowledge of where the artifact is and even not know what artifact descriptor is. We need to provide meaningful message for the user of Ratyify and not the user of ACR.

Originally posted by @toddysm in #1662 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yizha1