In current implementation any error returned by one of the user defined adapters (with user defined errors) are converted to string and attached to a ambiguous adapter_error variant of the core error enum. This doesn't allow the user to easily distinguish what error occurred. Instead, the error needs to be returned in a way that the original error can be matched.
Issue: User defined errors in trait are just being converted to string in tap manager and returned using an ambiguous error type (adapter_error).
desired behavior: User defined error type is maintained and returned in a way that the user can use it as needed.
In current implementation any error returned by one of the user defined adapters (with user defined errors) are converted to string and attached to a ambiguous
adapter_errorvariant of the core error enum. This doesn't allow the user to easily distinguish what error occurred. Instead, the error needs to be returned in a way that the original error can be matched.Issue: User defined errors in trait are just being converted to string in tap manager and returned using an ambiguous error type (adapter_error). desired behavior: User defined error type is maintained and returned in a way that the user can use it as needed.