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
Across the many resources implemented in the providers history, we have inconsistent error handling requiring too much manual interpretation of what information to include in each message. This leads to inconsistently formatted error messages, with sometimes with redundant or incomplete information which can lead to an inefficient development cycle for practitioners.
We should standardize on error message formatting and generation, automatically inserting context where possible and enhancing linters/sempgrep so that existing or new error messages found will be flagged so they could be made consistent.
Work currently being done on logging enhancements should enable this to be performed more efficiently.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
Across the many resources implemented in the providers history, we have inconsistent error handling requiring too much manual interpretation of what information to include in each message. This leads to inconsistently formatted error messages, with sometimes with redundant or incomplete information which can lead to an inefficient development cycle for practitioners.
We should standardize on error message formatting and generation, automatically inserting context where possible and enhancing linters/sempgrep so that existing or new error messages found will be flagged so they could be made consistent.
Work currently being done on logging enhancements should enable this to be performed more efficiently.
References
Relates #17314.
Relates #15891.
The text was updated successfully, but these errors were encountered: