-
Notifications
You must be signed in to change notification settings - Fork 148
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
Enhance Error Messages #577
Comments
Hi @dylanpulver, thank you for opening this issue! We appreciate your effort in reporting this. Our team will review it and get back to you soon. Note: If this is a serious security issue that could impact the security of Safety CLI users, please email [email protected] immediately. Thank you for contributing to Safety CLI! |
take |
@dylanpulver Can someone please point out to me one error message that would be a good candidate for enhancing? Just so I have an idea of what to look for... |
Hi @rpattekar, Absolutely! For this one we welcome updates to existing error messages as well as introducing new error messages to the codebase. I will post a few approaches here.
These are just starting places/ideas to consider for improving existing logging and adding more logging. We welcome any ideas to improve our error messages across the codebase! Thank you! |
its a good idea to improve log statements in the code, can you please help me locate the console messages for this? |
@vgauraha62 Definitely! In my message above I listed a few areas where log statements either exist or should be added. Is there anything else I can help to provide? |
Clear and informative error messages are essential for a good user experience. We are looking for contributions that improve existing error messages, making them more descriptive and helpful for users. If you improve an error message, please create a new issue to describe the enhancements you’ve made and link it back to this general error message improvement issue.
The text was updated successfully, but these errors were encountered: