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
Attoparsec has limited
error reporting support. One thing you could do is write an exception
wrapping stream that would catch any exception generated by read and wrap
some kind of informative error message around it. More practically, what
you will want to do for http-streams is to catch the exceptions you expect
(ParseException being chief amongst them) and then do something smart about
converting that error into a sensible http-streams exception.
This would be a Good Thing™.
AfC
The text was updated successfully, but these errors were encountered:
I meant that in your downstream code, if you receive an io-streams ParseException, that means you know where it came from and can re-wrap that to provide a useful error message to the user (BadHttpResponse or whatever).
In a comment on snapframework/io-streams#3 (comment), @gregorycollins wrote:
This would be a Good Thing™.
AfC
The text was updated successfully, but these errors were encountered: