You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error messages in some Notation CLI commands do not show the actual value that were provided or show too vague error messages that are hard to troubleshoot and locate the root cause. Notation maintainers are working on improving some error messages, such as #810 .
What solution do you propose?
In order to provide clearer structures for error categorizing and also more actionable error outputs for better user experience, it is recommended to create a Notation CLI Error Handling Guideline.
This document aims to provide the guidelines for ORAS contributors to improve existing error messages and handling method as well as the new error output format. It will also provide recommendations for ORAS CLI contributors for how to write friendly and standard error messages and avoid inconsistent error handling & messages.
What alternatives have you considered?
NA
Any additional context?
No response
The text was updated successfully, but these errors were encountered:
Resolve#824
This guideline only includes the guiding principles for Notation CLI error message. All suggested changes will be documented into different GitHub issues and another [document](https://hackmd.io/9O01p9xYS7S-8apWZkaLHg).
---------
Signed-off-by: Feynman Zhou <[email protected]>
Is your feature request related to a problem?
The error messages in some Notation CLI commands do not show the actual value that were provided or show too vague error messages that are hard to troubleshoot and locate the root cause. Notation maintainers are working on improving some error messages, such as #810 .
What solution do you propose?
In order to provide clearer structures for error categorizing and also more actionable error outputs for better user experience, it is recommended to create a Notation CLI Error Handling Guideline.
This document aims to provide the guidelines for ORAS contributors to improve existing error messages and handling method as well as the new error output format. It will also provide recommendations for ORAS CLI contributors for how to write friendly and standard error messages and avoid inconsistent error handling & messages.
What alternatives have you considered?
NA
Any additional context?
No response
The text was updated successfully, but these errors were encountered: