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
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
Migrating code to the newer preferred system of checking for errors using errors.Is instead of a attempt to cast the error to a specific type identified that the errors generated by viper do not support this functionality.
Proposed Solution
Ensure errors.Is is supported by all error types and include tests for these to verify functionality.
For those errors that wrap other errors or are of a struct type we need to add the Is(err error) method.
This allows errors to be checked using both the old and new system.
Alternatives Considered
The alternative is the old way of handling errors.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
A maintainer will take a look at your issue shortly. 👀
In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.
📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:
Preflight Checklist
Problem Description
Migrating code to the newer preferred system of checking for errors using errors.Is instead of a attempt to cast the error to a specific type identified that the errors generated by viper do not support this functionality.
Proposed Solution
Ensure errors.Is is supported by all error types and include tests for these to verify functionality.
For those errors that wrap other errors or are of a struct type we need to add the
Is(err error)
method.This allows errors to be checked using both the old and new system.
Alternatives Considered
The alternative is the old way of handling errors.
Additional Information
No response
The text was updated successfully, but these errors were encountered: