Enhance Error Messages

[dylanpulver]

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.

[github-actions]

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.
If you have any additional details or updates, feel free to add them to this issue.

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!

[rpattekar]

take

[rpattekar]

@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...

[dylanpulver]

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.

1. searching LOG.exception in the codebase
   We have 20 results here which can likely be improved upon!:

2. searching try
   We have ~100 try except loops but not all except blocks have logging currently.

3. searching LOG.error
   We have 8 cases of LOG.error in the codebase that could likely be improved!

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!

[vgauraha62]

its a good idea to improve log statements in the code, can you please help me locate the console messages for this?

[dylanpulver]

@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?