On Sun, 28 Jul 2013 13:59:13 GMT, Dicebot wrote:

On Sun, 28 Jul 2013 12:49:43 GMT, Manu Evans wrote:

I still can't see how you can customise the error response though without a bunch of logic in the catch, and as soon as that exists, then it could equally just appear at the point of consumption.

What kind of customization you keep in mind? I'd expect to use default output in most of cases, probably sometimes tweaking it before passing e to render. Any specific example?

Consider basically any sign-up form, if something is missing, a customised message almost always appears in red to the right of the missing item. In my case, I'm dealing with an API, where the error reporting becomes rather specific.

If this API was available though, I would definitely use it, and say it was a good API.

Well, usual story: "one day, when I'll have plenty of spare time" ;) Don't use vibe.d now, can't invest much time here, unfortunately.

I hacked together a test of your proposal, it's working well, although my argument structures are too small in many cases to see a benefit in terns of number of lines. The exception handling code is definitely larger than the conditional logic I had before.

I am definitely being lynched by the fact that there is no FLS, no user variables field in HTTPServerRequest (both would be useful). I can't carry variables with me throughout the route.