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'm intrigued by bounce & am trying to make my own query hoping to propagate error along to my rendered components! But unfortunately, I do not see how I could do that without great toil: I'm using a reqwest client (to be precise, a client generated by progenitor), which returns errors that are neither PartialEq nor Clone, nor std::error::Error.
So I thought, hah, let's just use anyhow; it does all the reasonable error wrapping with minimal headache. Turns out, anyhow doesn't impl PartialEq either.
The best/easiest I could come up with is this, but I don't love it (sorry for the name, hah):
Do you have hints / recommendations on what to do that would help preserve the identifiability of my errors, or do you think the requirements for the Error associated type can be loosened?
The text was updated successfully, but these errors were encountered:
I'm intrigued by bounce & am trying to make my own query hoping to propagate error along to my rendered components! But unfortunately, I do not see how I could do that without great toil: I'm using a reqwest client (to be precise, a client generated by
progenitor
), which returns errors that are neither PartialEq nor Clone, nor std::error::Error.So I thought, hah, let's just use anyhow; it does all the reasonable error wrapping with minimal headache. Turns out, anyhow doesn't impl PartialEq either.
The best/easiest I could come up with is this, but I don't love it (sorry for the name, hah):
Do you have hints / recommendations on what to do that would help preserve the identifiability of my errors, or do you think the requirements for the Error associated type can be loosened?
The text was updated successfully, but these errors were encountered: