Closed zbindenren closed 8 years ago
I think it's a positive thing that we standardize the error coming out of Process
to be a ParseError
for all type/deserialization failures. How about if we add an error
field to the ParseError
struct for the underlying cause?
I have the following Type:
If I use the the enviromment varialbe
APP_MODE=d
andAPP_MODE=p
everything works as designed.But if I use
APP_MODE=t
I get the error:But I would prefer the error message from the Decode function, like:
Is that somehow possible?